Re: [SSI-devel] strange inetd/tftp behavior

[Christian L. <ly...@po...>]

HI,
> Everytime a node joins (actually changes its membership state),
> SIGCLUSTER (stolen from one of the realtime signals) gets sent to all
> the processes on the system. (This was a holdover from the UnixWare
> implementation.) Aneesh suspects your inetd is dying because of this. I=
f
> you strace your inetd and it is dying because it is receiving a signal
> (49 I believe) then Aneesh is correct.
>

=09Thanks for the explanation, but I think the problem is not with SIGCLU=
STER,=20
because I can reproduce the problem using just the master node, and anoth=
er=20
(non-cluster) machine with a tftp client (of course, all other nodes are=20
turned offf)! So there's no SIGCLUSTER signals. Ftpd dies(?) after the fi=
rst=20
transfer. I try to setup a telnetd just to see if it die too but this not=
=20
happens! just tftpd die :-(

> This is to be changed in the near future using the linux fasync
> mechanism. Applications concerned about changes in the cluster
> membership will open a file descriptor in /proc and use the F_SETOWN an=
d
> F_SETSIG fcntls to specify that they receive signals and what signal it
> will be.
>
> John Byrne

--=20
Christian Lyra
POP-PR - RNP

  The master programmer moves from program to program without fear. No ch=
ange=20
in management can harm him. He will not be fired, even if the project is=20
cancelled. Why is this? He is filled with Tao.=20
=09=09=09=09=09=09The Tao Of Programing