[lkml]   [2000]   [Sep]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Signal handling different for root and others
On Tue, Sep 12, 2000 at 02:20:02AM +0200, jury gerold wrote:
> I ran into a problem with 2.2.x kernels, posix signals and sockets.
> I have a program that creates a serversocket, puts it into listen state,
> attaches the socket to a realtime signal and simply waits for the signal.
> When i create a connection (telnet a.b.c.d port) the signal is delivered depending
> on the user that does the telnet.
> If root creates the socket, then only root or another machine is able to trigger the signal
> by connecting to the socket.
> Normal users are only able to create a SIGIO signal when connecting.

That's very unlikely. TCP does not propagate gid/uid information over sockets,
not even over localhost.
There was probably some other factor during your tests. When you overflow
the rt signal queue then the kernel will fall back to sending SIGIO. In
this case you have to collect outstanding events using poll.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.092 / U:18.888 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site