Hi,
I'm running Digital Unix v4.0F, not that this problem is specific to that
particular version of DU or TU I believe.
We have a daemon called erdmaster, which attaches to port 5530 and acts as a
license manager. Due to problems of people getting a license allocated and
then hogging that license by keeping the application open, I started
stopping the daemon at 4 o'clock in the morning and restarting around 5
o'clock. The reason for the delay was, that trying to start the daemon
straight after stopping produced an error to the effect that the daemon
could not access port 5530, that it was already allocated to another
application. Running netstat -na, you could still see entries for the port
5530, and I guess from the systems point of view it thought that the port
was still in use. After some time delay, must be of the order of 5-10 mins
the system does release the port and the license daemon can be restarted.
I was wondering if there was a way of
(a) hurrying up the system so that it would release the port sooner, or
(b) forcing the system to release the port.
Conceptually I can see that the system may not like this, as there may still
be traffic comming in on that port from the clients who are trying to get
some sort of a license token. However, once the daemon has stopped, than
clients get the message that the license manager is uncontactable. So it
seems a waste of time the system still thinking the port is already
allocated, and that the port may as well be released immediately, from my
point of view.
Anyone got any ideas.
Dennis
######################################
Dennis Macdonell
Systems Administrator
AUSLIG
mail: PO Box 2, Belconnen, ACT 2617
email: mcdonell_at_auslig.gov.au
ph: 61 2 6201 4326
fax: 61 2 6201 4377
######################################
Received on Mon Aug 27 2001 - 08:20:28 NZST