[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PID of client requirements

From: Neal H. Walfield
Subject: Re: PID of client requirements
Date: 04 Nov 2002 22:38:47 -0500
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2

> Trusting the user to provide his pid is only half of the job when
> signals are concerned.  The second thing needed is a signal
> authorization port which the user requests from the server, and which
> the server will provide in the signal message.  See, for example, how
> this works for terminals.

Ahem, I think you are missing the point.  We are assuming two
processes: a manager and a rogue.  The rogue process locks the file
supplying a fake pid and then blocks.  The manager process sees that
the file is locked for "too long" (define liberally) and kills the
locking process--or rather, what it thinks is the locking process.  If
the manager is running as root, this could be anyone.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]