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

[John B. <joh...@hp...>]

Christian Lyra wrote:
> 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. If
>>you strace your inetd and it is dying because it is receiving a signal
>>(49 I believe) then Aneesh is correct.
>>
> 
> 
> 	Thanks for the explanation, but I think the problem is not with SIGCLUSTER, 
> because I can reproduce the problem using just the master node, and another 
> (non-cluster) machine with a tftp client (of course, all other nodes are 
> turned offf)! So there's no SIGCLUSTER signals. Ftpd dies(?) after the first 
> transfer. I try to setup a telnetd just to see if it die too but this not 
> happens! just tftpd die :-(

The ftp/tftp transfer completes successfully and then the daemon dies? 
Or does the daemon die partway through thr transfer.

The daemon dying after a successful transfer may not be bad. Most inetd 
sub-daemons do if they don't receive another request after a given time.

If inetd is running and the tftpd is dead, then a new tftpd should be 
spawned. The problem then might be inetd is not seeing its children die. 
  If you run strace on inetd during the successful operation followed by 
the failure maybe we could figure out what is going wrong.

John Byrne