Re: non-root process and PID files
From: Terry Lambert (tlambert2_at_mindspring.com)
Date: 10/30/03
- Previous message: Terry Lambert: "Re: freeing data segment"
- In reply to: Christopher Vance: "Re: non-root process and PID files"
- Next in thread: Christopher Vance: "Re: non-root process and PID files"
- Reply: Christopher Vance: "Re: non-root process and PID files"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 30 Oct 2003 03:45:24 -0800 To: Christopher Vance <vance@aurema.com>
Christopher Vance wrote:
> You can already mark a fd 'close on exec'.
>
> May I suggest a different feature: the ability to mark an open file
> (not just its fd) 'remove on close', with permission checked at mark
> time rather than close time (this status forgotten if not permitted
> when set) and the unlink actually done at close time only if the file
> has exactly one link and one open file instance at that time.
If all you have is an fd, you can not get from an fd to a path
without an exhaustive search of the disk, in most FS's.
Also, leaving the path peresent permits someone to hard-link it
to some other file, to make it stay around. Since /var has a
/var/tmp, this would be a real danger, I think.
-- Terry
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: Terry Lambert: "Re: freeing data segment"
- In reply to: Christopher Vance: "Re: non-root process and PID files"
- Next in thread: Christopher Vance: "Re: non-root process and PID files"
- Reply: Christopher Vance: "Re: non-root process and PID files"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|