nolan@tssi.UUCP (Michael Nolan) (06/25/91)
Browsing around on my NCR Tower (SVR2) trying to solve a problem with lock files not being deleted by uucico, I discovered that there appear to be two links to a directory, although I had thought that was not permitted in unix. (multiple file links, yes, but not multiple directory links) (ls -ail /usr/spool) total 8 1935 drwxrwxr-x 7 root rootgrp 160 Jun 24 15:42 . 64 drwxr-xr-x 28 bin bin 480 Mar 7 16:44 .. 1936 drwxr-xr-x 4 root sys 64 Jul 18 1988 cron 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 locks 1942 drwxr-xr-x 8 lp bin 320 Dec 27 17:09 lp 1980 drwxrwxr-x 3 root rootgrp 144 Feb 12 1990 lpd 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 uucp 1997 drwxrwxrwx 2 uucp daemon 96 May 25 03:37 uucppublic Note that both locks and uucp have the same inode number. As one might expect, /usr/spool/locks and /usr/spool/uucp have identical contents. If I create a file in one, it shows up in the other. Is this normal and, if not, is it a serious problem? (Is it causing the LCK..tty07 file not to be deleted after an incoming uucico call?) ------------------------------------------------------------------------------ Michael Nolan "Software means never having Tailored Software Services, Inc. to say you're finished." Lincoln, Nebraska (402) 423-1490 --J. D. Hildebrand in UNIX REVIEW UUCP: tssi!nolan (or try sparky!dsndata!tssi!nolan) Internet: nolan@helios.unl.edu (if you can't get the other address to work)
plus@wrangler.WLK.COM (ATplusT PC63xx Mailing list) (06/28/91)
} } Browsing around on my NCR Tower (SVR2) trying to solve a problem with lock } files not being deleted by uucico, I discovered that there appear to be two } links to a directory, although I had thought that was not permitted in unix. } (multiple file links, yes, but not multiple directory links) } } (ls -ail /usr/spool) } total 8 } 1935 drwxrwxr-x 7 root rootgrp 160 Jun 24 15:42 . } 64 drwxr-xr-x 28 bin bin 480 Mar 7 16:44 .. } 1936 drwxr-xr-x 4 root sys 64 Jul 18 1988 cron } 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 locks } 1942 drwxr-xr-x 8 lp bin 320 Dec 27 17:09 lp } 1980 drwxrwxr-x 3 root rootgrp 144 Feb 12 1990 lpd } 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 uucp } 1997 drwxrwxrwx 2 uucp daemon 96 May 25 03:37 uucppublic } } Note that both locks and uucp have the same inode number. As one might expect, } /usr/spool/locks and /usr/spool/uucp have identical contents. If I create } a file in one, it shows up in the other. } } Is this normal and, if not, is it a serious problem? (Is it causing the } LCK..tty07 file not to be deleted after an incoming uucico call?) } ------------------------------------------------------------------------------ } Michael Nolan "Software means never having } Tailored Software Services, Inc. to say you're finished." } Lincoln, Nebraska (402) 423-1490 --J. D. Hildebrand in UNIX REVIEW } UUCP: tssi!nolan (or try sparky!dsndata!tssi!nolan) } Internet: nolan@helios.unl.edu (if you can't get the other address to work) } This is definitely not normal. However, it should not be very hard to correct. First try doing a rmdir on the locks directory. I do not expect this to work because the directory will not be empty. If that does not work, do a backup of /usr/spool/uucp. Then do a rm -r on /usr/spool/uucp and /usr/spool/locks. Then use mkdir to remake the two directories and restore your backup. Email me if this does not work. -- ################################################# # Vernon E. Hurdle (vernon@ssi600.lonestar.org) # # Seay Systems, Inc. Dallas, TX # # Voice: 214/522-2324 # #################################################
vause@cs-col.Columbia.NCR.COM (Sam Vause) (06/28/91)
In article <904@wrangler.WLK.COM> plus@wrangler.WLK.COM (ATplusT PC63xx Mailing list) writes: >} >} Browsing around on my NCR Tower (SVR2) trying to solve a problem with lock >} files not being deleted by uucico, I discovered that there appear to be two >} links to a directory, although I had thought that was not permitted in unix. >} (multiple file links, yes, but not multiple directory links) >} >} (ls -ail /usr/spool) >} total 8 >} 1935 drwxrwxr-x 7 root rootgrp 160 Jun 24 15:42 . >} 64 drwxr-xr-x 28 bin bin 480 Mar 7 16:44 .. >} 1936 drwxr-xr-x 4 root sys 64 Jul 18 1988 cron >} 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 locks >} 1942 drwxr-xr-x 8 lp bin 320 Dec 27 17:09 lp >} 1980 drwxrwxr-x 3 root rootgrp 144 Feb 12 1990 lpd >} 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 uucp >} 1997 drwxrwxrwx 2 uucp daemon 96 May 25 03:37 uucppublic >} >} Note that both locks and uucp have the same inode number. As one might expect, >} /usr/spool/locks and /usr/spool/uucp have identical contents. If I create >} a file in one, it shows up in the other. >} >} Is this normal and, if not, is it a serious problem? (Is it causing the >} LCK..tty07 file not to be deleted after an incoming uucico call?) >} ------------------------------------------------------------------------------ >} Michael Nolan "Software means never having >} Tailored Software Services, Inc. to say you're finished." >} Lincoln, Nebraska (402) 423-1490 --J. D. Hildebrand in UNIX REVIEW >} UUCP: tssi!nolan (or try sparky!dsndata!tssi!nolan) >} Internet: nolan@helios.unl.edu (if you can't get the other address to work) >} >This is definitely not normal. However, it should not be very hard to >correct. First try doing a rmdir on the locks directory. I do not >expect this to work because the directory will not be empty. > >If that does not work, do a backup of /usr/spool/uucp. Then do a rm -r on >/usr/spool/uucp and /usr/spool/locks. Then use mkdir to remake the two >directories and restore your backup. > >Email me if this does not work. > >################################################# ># Vernon E. Hurdle (vernon@ssi600.lonestar.org) # ># Seay Systems, Inc. Dallas, TX # ># Voice: 214/522-2324 # >################################################# How about first trying a simple "# /etc/unlink /usr/spool/locks <CR>"? Then, remake the directory with the original permissions. All should be okay... -- +---------------------------------------------------------------+ |Sam Vause, NCR Corporation, Customer Services - UNIX Support | |3325 Platt Springs Road, West Columbia, SC 29169 (803) 791-6953| | vause@cs-col.ColumbiaSC.NCR.COM |
dick@ccsds.ahold.nl (Dick Heijne CCS/TS) (06/28/91)
In article <904@wrangler.WLK.COM>, plus@wrangler.WLK.COM (ATplusT PC63xx Mailing list) writes: > } 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 locks > } 1984 drwxrwxrwx 16 uucp daemon 384 Jun 24 16:02 uucp > } > } Is this normal and, if not, is it a serious problem? > This is definitely not normal. The only way to link directories together is via symbolic links via the special NCR sln command (a derrivate from BSD's ln -s), but then the ls output would show so by an 'l' in the forst column and an arrowpath in the name... Dick.
nolan@helios.unl.edu (Michael Nolan) (06/29/91)
Thanks to all who responded, even if I didn't send you an acknowledgement. I think I caused the situation myself fooling around with the way ckermit does lock files, I ended up doing a tar backup, deleting both directories and recreating then restoring what I needed back. The unlink command got sorta lost, and wouldn't work. (And then I had to create an empty directory [/usr/spool/uucp/.Workspace] which apparently didn't get created because it was empty.) Doing this didn't affect the lock file problem, but that's another story... Michael Nolan nolan@helios.unl tssi!nolan