Your message dated Mon, 20 Jul 2009 10:17:12 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-ltsp-devel] Bug#537644: Please denote 'openbsd-inetd 
| inet-superserver' to recommends
has caused the Debian Bug report #537644,
regarding Please denote 'openbsd-inetd | inet-superserver' to recommends
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
537644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537644
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ltsp-server-standalone
Severity: normal

Hi,

as far as I know (but please correct me if I'm wrong),
ltsp-server-standalone only depends on 'openbsd-inetd |
inet-superserver' because of the tftp of choice.

Since tftpd-hpa 5.0-1, the tftpd is run standalone by default, not
supporting inetd mode anymore (in debian). Therefore, if possible,
please denote the depends to a recommends.

Please also denote it on the ltsp-server package if it applies there as
well.

Regards,
Daniel

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          [email protected]
Internet:       http://people.panthera-systems.net/~daniel-baumann/



--- End Message ---
--- Begin Message ---
Oliver Grawert wrote:
>> as far as I know (but please correct me if I'm wrong),
>> ltsp-server-standalone only depends on 'openbsd-inetd |
>> inet-superserver' because of the tftp of choice.
> sadly you are wrong, nbdswapd is running from ited as well (in debian
> and ubuntu), and in ubuntu nbdrootd is also running from inetd.

so let's close the bug then, and sorry for the noise.

> what was the reason to change the default mode ?

there are basically three reasons:

1. it's a major pita to handle inetd properly through maintainer scripts
and has been source for all sorts of problems.

2. tftpd-hpa itself has problems (upstream wise), sometimes it fails to
work when being in inetd mode, but works flawless and reliable when in
daemon mode (and as daemon, it's very tiny and doesn't consume notable
ressources).

3. when in inetd mode, it doesn't support all the features (such as ipv6).

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          [email protected]
Internet:       http://people.panthera-systems.net/~daniel-baumann/


--- End Message ---

Reply via email to