Hello again Tru-managers,
After rebooting a DU40.D host, I ended up having portmap and inetd
clashing on the usage of port TCP 901, for no reason that I can find. I
used to run SWAT, Samba's graphical administration interface on port
TCP:901. SWAT is defined in /etc/services as:
swat 901/tcp
and it is fired up by inetd using (in /etc/inetd.conf):
swat stream tcp nowait root /loc/app/samba/bin/swat swat
Now, messages such as "inetd[450]: swat/tcp: bind: Address already in
use" are cropping up in daemon.log, and doing a rpcinfo on this host
shows entries like these:
100005 1 tcp 901 mountd
100005 3 tcp 901 mountd
mountd is indeed using the TCP:901 port, so inetd complains about it! A
quick survey of our Unix hosts (all running some version of DU/TU) show
that the port used by mountd varies between hosts: 901, 900, 899, 933,
878 have all been observed for mountd.
My question is: how does one control the availibiliy of ports for use by
the portmap daemon? The simple and obvious solution to my problem is to
run SWAT at some untouched port, say 9901 instead of 901, but I remain
curious as to how does portmap works.
Thanks in advance.
--
===============================================
Charles Vachon tel: (418) 627-6355 x2760
email: cvachon2_at_mrn.gouv.qc.ca
Administrateur de système
FRCQ/Ministère des Ressources
Naturelles du Québec
===============================================
Received on Mon Jun 26 2000 - 19:27:52 NZST