"Scott K. Ellis" <[EMAIL PROTECTED]> writes:
[snip]
> The only solution is to come up with a program that
> never follows syslinks, and checks that the i-node of the file it is
> removing remains the same.
Actually, i-nodes can be recycled, so it isn't a good idea to depend
on that:
% cd /tmp
% touch foo
% ls -li foo
14 -rw-rw-r-- 1 carey carey 0 Aug 9 17:47 foo
% rm foo
% touch foo
% ls -li foo
14 -rw-rw-r-- 1 carey carey 0 Aug 9 17:48 foo
If a program will be creating a file (like /tmp/.X0-lock) but
another creates and deletes a file in the same file system just before
this, it will probably have the same i-node.
--
Carey Evans <*> [EMAIL PROTECTED]
"[UNIX] appears to have the inside track on being the replacement for
CP/M on the largest microcomputers (e.g. those based on 68000...)"
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
