Re: kill(2)

[SL Baur <steve@example.com>]

Viktor Pavlenko <vp@example.com> writes in tlug@example.com:

> shimpei@example.com writes:
>>> The reason I asked is that I have to set GID on the executable
>>> (someone else from my group should be able to send a signal 
>>> to my process) and hate doing that.
>> 
>> Unless I'm misunderstanding your situation, setgid isn't enough; you
>> need setuid. And yes, I can see why you would hate that....

> Yes, sure (I was thinking about something else). Thanks for correction.

Why do you need people to send signals?  Depending upon how fancy you
want to get there are plenty of non-setuid ways to go about it.  On
HP/UX one possible way would be to set up a listening Unix domain
socket, then enable SIGIO on that socket.  That way when a connection
is attempted, the process gets SIGIO.  You don't need setuid for that.