linux-decnet-user Mailing List for DECnet for Linux
Brought to you by:
chrissie_c,
ph3-der-loewe
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(8) |
Jun
(39) |
Jul
(30) |
Aug
(23) |
Sep
(9) |
Oct
(9) |
Nov
(30) |
Dec
(24) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(12) |
Feb
(4) |
Mar
(21) |
Apr
|
May
(3) |
Jun
(3) |
Jul
(13) |
Aug
(13) |
Sep
(18) |
Oct
(10) |
Nov
(25) |
Dec
(2) |
| 2002 |
Jan
(7) |
Feb
(14) |
Mar
(15) |
Apr
(29) |
May
(10) |
Jun
(23) |
Jul
(76) |
Aug
(52) |
Sep
(15) |
Oct
(47) |
Nov
(12) |
Dec
(1) |
| 2003 |
Jan
(5) |
Feb
(12) |
Mar
(21) |
Apr
(26) |
May
(66) |
Jun
(16) |
Jul
(13) |
Aug
(7) |
Sep
(21) |
Oct
(11) |
Nov
(4) |
Dec
(11) |
| 2004 |
Jan
(18) |
Feb
(1) |
Mar
(1) |
Apr
(20) |
May
(10) |
Jun
(4) |
Jul
(9) |
Aug
(9) |
Sep
|
Oct
(5) |
Nov
(13) |
Dec
(8) |
| 2005 |
Jan
(23) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(11) |
Jun
(3) |
Jul
(5) |
Aug
(15) |
Sep
(3) |
Oct
(13) |
Nov
(2) |
Dec
(7) |
| 2006 |
Jan
(5) |
Feb
(8) |
Mar
(6) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(2) |
Oct
(6) |
Nov
|
Dec
(3) |
| 2007 |
Jan
|
Feb
(6) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(5) |
Jul
(7) |
Aug
|
Sep
(7) |
Oct
(7) |
Nov
(4) |
Dec
(2) |
| 2008 |
Jan
(10) |
Feb
(5) |
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
(14) |
Aug
(3) |
Sep
(6) |
Oct
(7) |
Nov
|
Dec
|
| 2009 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
(2) |
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
(15) |
Sep
(9) |
Oct
(1) |
Nov
(2) |
Dec
|
| 2010 |
Jan
|
Feb
(5) |
Mar
(2) |
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
(2) |
Sep
(6) |
Oct
(1) |
Nov
(15) |
Dec
|
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(11) |
Apr
|
May
|
Jun
(17) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(8) |
| 2012 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(12) |
Feb
(15) |
Mar
(11) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(5) |
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2016 |
Jan
|
Feb
(14) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
1
|
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
|
16
|
17
|
18
(3) |
19
(2) |
20
(4) |
21
(1) |
22
|
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
|
30
|
31
|
|
|
|
|
|
|
From: Patrick C. <pa...@ty...> - 2004-05-21 07:06:16
|
On Thu, May 20, 2004 at 04:17:43PM -0400, Stanley F. Quayle wrote: > Let me explain what I'm doing now, and see if this is possible in > Linux DECnet. > > I have a Linux box (RH 7.2) NFS exporting a chunk of disk to my VMS > systems. The VMS systems do daily backups to the Linux box. Also, I > have a whole chunk of data on the Linux box that the VMS systems > "see" as VMS files, characteristics and all. > > How this works is that, when I create a file from the VMS system, two > files get created on the Linux system. Suppose I create ABC.XYZ;27 > on VMS. On the Linux box, I get: > > abc.xyz;27 and > .$ADF$abc.xyz;27 (this is "hidden" because of the leading dot) > > (There's also a "abc.xyz" hard-linked to the "abc.xyz;27" to support > version numbers, but let's not go there.) By the way -- this is all > handled by the VMS TCP/IP stack. > > Anyway, the .$ADF$ file is 90 bytes long, and holds the VMS > characteristics of the file. > > When I access the file from VMS, it gets reported back as whatever > characteristics it had when I created it. If I delete the .$ADF$ > file, it comes back as Stream-LF. > > Not knowing anything about the underlying DECnet protocol, it would > seem that FAL on the receiving system gets the characteristics on > files being sent. And on files being "pulled", it reports the > characteristics back. > > How hard would it be to modify the FAL on Linux to do something like > this? FAL already does this to a limited extent. if you add the -m switch to the daemon (in /etc/dnetd.conf) it will create a .fal directory and put metadata files in there. It can also, to a limited extent, understand the $ADF$ files that the VMS NFS client puts there if you also use -t. A good combination of options for FAL is "-m -t -ae" which will use .fal files where files are createdbut it, $ADF$ files when created by NFS, and use file extension-based guessing for files with no other information. -- patrick |
|
From: Stanley F. Q. <sys...@st...> - 2004-05-20 20:23:41
|
Let me explain what I'm doing now, and see if this is possible in Linux DECnet. I have a Linux box (RH 7.2) NFS exporting a chunk of disk to my VMS systems. The VMS systems do daily backups to the Linux box. Also, I have a whole chunk of data on the Linux box that the VMS systems "see" as VMS files, characteristics and all. How this works is that, when I create a file from the VMS system, two files get created on the Linux system. Suppose I create ABC.XYZ;27 on VMS. On the Linux box, I get: abc.xyz;27 and .$ADF$abc.xyz;27 (this is "hidden" because of the leading dot) (There's also a "abc.xyz" hard-linked to the "abc.xyz;27" to support version numbers, but let's not go there.) By the way -- this is all handled by the VMS TCP/IP stack. Anyway, the .$ADF$ file is 90 bytes long, and holds the VMS characteristics of the file. When I access the file from VMS, it gets reported back as whatever characteristics it had when I created it. If I delete the .$ADF$ file, it comes back as Stream-LF. Not knowing anything about the underlying DECnet protocol, it would seem that FAL on the receiving system gets the characteristics on files being sent. And on files being "pulled", it reports the characteristics back. How hard would it be to modify the FAL on Linux to do something like this? --Stan Quayle Quayle Consulting Inc. ---------- Stanley F. Quayle, P.E. N8SQ +1 614-868-1363 8572 North Spring Ct., Pickerington, OH 43147 USA stan-at-stanq-dot-com http://www.stanq.com |
|
From: Patrick C. <pa...@ty...> - 2004-05-20 12:28:32
|
On Thu, May 20, 2004 at 08:20:43AM -0400, Stanley F. Quayle wrote: > > On Wed, May 19, 2004 at 07:58:59AM +0000, ada...@br... wrote: > > > I get the login prompt > > > enter username followed by password > > > A few lines print out indicating the login was successful, but a few > > > seconds later im returned to the local prompt with the message 'Alarm > > > Clock'. > > The system is doing a SET TERM/INQUIRE . This happens to me as well. > The two likely places to check are: > > - SYS$MANAGER:SYLOGIN.COM > - The username's LOGIN.COM file > > If you're connecting to a production system, be careful. The LAT > client doesn't have this problem, by the way... Aha! Now it makes sense. Thank you. The fix I posted is correct then. I've committed it to CVS. -- patrick |
|
From: Stanley F. Q. <sys...@st...> - 2004-05-20 12:21:43
|
> On Wed, May 19, 2004 at 07:58:59AM +0000, ada...@br... wrote: > > I get the login prompt > > enter username followed by password > > A few lines print out indicating the login was successful, but a few > > seconds later im returned to the local prompt with the message 'Alarm > > Clock'. The system is doing a SET TERM/INQUIRE . This happens to me as well. The two likely places to check are: - SYS$MANAGER:SYLOGIN.COM - The username's LOGIN.COM file If you're connecting to a production system, be careful. The LAT client doesn't have this problem, by the way... --Stan Quayle Quayle Consulting Inc. ---------- Stanley F. Quayle, P.E. N8SQ +1 614-868-1363 8572 North Spring Ct., Pickerington, OH 43147 USA stan-at-stanq-dot-com http://www.stanq.com |
|
From: Patrick C. <pa...@ty...> - 2004-05-20 07:36:34
|
On Wed, May 19, 2004 at 07:58:59AM +0000, ada...@br... wrote:
> Hi
>
> I get the login prompt
> enter username followed by password
> A few lines print out indicating the login was successful, but a few
> seconds later im returned to the local prompt with the message 'Alarm
> Clock'.
>
> This is happening on vms 5 and 6 machines
>
> Using dnlogin on the same hosts works fine.
I've seen this once or twice, but am not sure what's causing it - it
could be the classic BSD signal race but I'm not quite sure how that could
happen with SIGALRM. Nevertheless you might like to try this patch:
diff -u -r1.8 sethost.c
--- sethost.c 26 Sep 2003 08:02:05 -0000 1.8
+++ sethost.c 20 May 2004 07:34:21 -0000
@@ -252,7 +252,6 @@
static void ct_timeout_proc(int x)
{ if (debug == 2) { printf(" Entered static void ct_timeout_proc...\n");}
ct_terminate_read(5);
- signal(SIGALRM,ct_timeout_proc);
}
/*-------------------------------------------------------------------------*/
static void ct_echo_input_char(char *c)
@@ -1846,6 +1845,11 @@
ct_init_term(); /* Set terminal in raw mode*/
sigemptyset(&ss);
+ sa.sa_handler = ct_timeout_proc;
+ sa.sa_mask = ss;
+ sa.sa_flags = 0;
+ sigaction(SIGALRM, &sa, NULL);
+
if (debug == 1)
{
printf("Connection to %d flavor",flavor); /*ed*/
--
patrick
|
|
From: <ada...@br...> - 2004-05-19 06:59:14
|
Hi Using the latest dnprogs on a redhat enterprise 3 self compiled kernel to fix decnet, and a stock mandrake 10 2.6.3 kernel i get the same problem with sethost. Using sethost to log into another linux box works fine, but using sethost to log into a vms box the following happens: I get the login prompt enter username followed by password A few lines print out indicating the login was successful, but a few seconds later im returned to the local prompt with the message 'Alarm Clock'. This is happening on vms 5 and 6 machines Using dnlogin on the same hosts works fine. Adam Pigg The information contained in this email may be commercially sensitive and/or legally privileged. It is intended solely for the person(s) to whom it is addressed. If you are not a named recipient, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. You must not disclose it to any other person, copy or distribute it or use it for any purpose. |
|
From: Patrick C. <pa...@ty...> - 2004-05-19 06:45:28
|
On Tue, May 18, 2004 at 07:39:02PM +0100, Steven Whitehouse wrote: > Hi, > > Also, just to add that this is a known problem in older Red Hat kernels, > but has been corrected for current & future builds. Fedora should be ok, > although I've not tested it personally, The latest Fedora kernels don't have DECnet in at all :( I think they got so upset with the SIOCGIFCONF problems that they disabled it in a sulk. I've opened a bug in Red Hat's bugzilla for it to be re-instated but it may be a while as FC2 has just been released - without it. -- patrick |
|
From: Steven W. <st...@ch...> - 2004-05-18 18:39:14
|
Hi, Also, just to add that this is a known problem in older Red Hat kernels, but has been corrected for current & future builds. Fedora should be ok, although I've not tested it personally, Steve. On Tue, May 18, 2004 at 07:18:14PM +0100, Patrick Caulfield wrote: > On Tue, May 18, 2004 at 01:27:04PM -0400, Stanley F. Quayle wrote: > > After starting DECnet, doing an "ifconfig" (/sbin/ifconfig) returns: > > > > : error fetching interface information: Device not found > > > > Doing an "ifconfig eth0" returns the normal information. > > > > I've done the following: > > > > - Installed on RH 7.2, RH 7.3, and RH 9 via RPM's. > > - Built DECnet from the latest sources > > - Installed a separate interface (eth1) and configured DECnet to > > use that interface > > > > This wouldn't seem to be such a problem, but the server I'm using is > > running other services -- and a "service named restart" causes named > > to only run against lo, not eth0. Other services behave similarly. > > > > This also happens with SuSE, kernel 2.4.21-99-default. > > This sounds like the symptom of a kernel built incorrectly with > DECNET_SIOCGIFCONF support. If that's the case, all I can suggest is to get the > kernel source and build the kernel without this option. > > Patrick > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Linux-decnet-user mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user |
|
From: Patrick C. <pa...@ty...> - 2004-05-18 18:18:25
|
On Tue, May 18, 2004 at 01:27:04PM -0400, Stanley F. Quayle wrote: > After starting DECnet, doing an "ifconfig" (/sbin/ifconfig) returns: > > : error fetching interface information: Device not found > > Doing an "ifconfig eth0" returns the normal information. > > I've done the following: > > - Installed on RH 7.2, RH 7.3, and RH 9 via RPM's. > - Built DECnet from the latest sources > - Installed a separate interface (eth1) and configured DECnet to > use that interface > > This wouldn't seem to be such a problem, but the server I'm using is > running other services -- and a "service named restart" causes named > to only run against lo, not eth0. Other services behave similarly. > > This also happens with SuSE, kernel 2.4.21-99-default. This sounds like the symptom of a kernel built incorrectly with DECNET_SIOCGIFCONF support. If that's the case, all I can suggest is to get the kernel source and build the kernel without this option. Patrick |
|
From: Stanley F. Q. <sys...@st...> - 2004-05-18 17:28:03
|
After starting DECnet, doing an "ifconfig" (/sbin/ifconfig) returns: : error fetching interface information: Device not found Doing an "ifconfig eth0" returns the normal information. I've done the following: - Installed on RH 7.2, RH 7.3, and RH 9 via RPM's. - Built DECnet from the latest sources - Installed a separate interface (eth1) and configured DECnet to use that interface This wouldn't seem to be such a problem, but the server I'm using is running other services -- and a "service named restart" causes named to only run against lo, not eth0. Other services behave similarly. This also happens with SuSE, kernel 2.4.21-99-default. Any suggestions? --Stan Quayle Quayle Consulting Inc. ---------- Stanley F. Quayle, P.E. N8SQ +1 614-868-1363 8572 North Spring Ct., Pickerington, OH 43147 USA stan-at-stanq-dot-com http://www.stanq.com |