Package: nas Version: 1.7-2 [Maintainer of didiwiki Cc:ed because of package collision]
As the subject says, nasd binds to port 8000 which is not in /etc/services. My guess is that it's not there because it is not standardized? Or am I mistaken? This wouldn't be a big problem until other packages also claims that port, for other purposes. Lets say, for example the real world example didiwiki. The proper fix would be to have a well known reserved port for the Network Audio system, but that might be troublesome? (: Could and should this be worked around in some way? Sure there are enough ports so that not two Debian packages have to collide in their default configuration when providing different services. Sure nasd could be made to listen to another port, but the fact that it took me a week or so to find the cause of that my sound stopped working makes me file a bug report. I could file another bug that didiwiki does not have it's port number configurable. Hanna, should I? One could also wish that "invoke.rc-d nas start" reported that port binding failed either to stderr/stdout or syslog. Should I file a separate report on that? Worth to know is that http://www.iana.org/assignments/port-numbers (but not Debian's file mentions another nas) nas 991/tcp Netnews Administration System nas 991/udp Netnews Administration System And what is vnas? Not a very descriptive name... vnas 577/tcp vnas vnas 577/udp vnas -- /Martin
signature.asc
Description: Digital signature
