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

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

> 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=
=2E

=09Sorry... maybe I didnt explain myself.... Inetd never dies, the first=20
transfer works, and there isnt any tftp hanged after the transfer
=2E but the next transfer doenst happen until inetd is restarted... look:

chuan:/tmp# tftp 10.0.1.1
tftp> get vmlinuz.nb
Received 2791134 bytes in 4.9 seconds
tftp> get vmlinuz.nb
Transfer timed out.

tftp>=20

them I restarted inetd while the get is running

tftp> get vmlinuz.nb
Received 2791134 bytes in 7.2 seconds
tftp>=20

>
> 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=
=2E
>   If you run strace on inetd during the successful operation followed b=
y
> the failure maybe we could figure out what is going wrong.

=09I will try this, may I ask your help again?  I'm not used to run strac=
e. May=20
I just  strace inetd at the prompt?

--=20
Christian Lyra
POP-PR - RNP

  The programmers of old were mysterious and profound. We cannot fathom t=
heir=20
thoughts, so all we do is describe their appearance.=20
  Aware, like a fox crossing the water. Alert, like a general on the=20
battlefield. Kind, like a hostess greeting her guests. Simple, like uncar=
ved=20
blocks of wood. Opaque, like black pools in darkened caves.=20
=09=09=09=09=09=09The Tao Of Programing