On 14-Sep-99 Warner Losh wrote:
In message [EMAIL PROTECTED] "Daniel O'Connor"
writes:
: Why is restarting it necessary? The man page doesn't say anything to that
: effect.
The inetd program rereads its configuration file when it receives a
hangup signal, SIGHUP. Services may
On Tue, 14 Sep 1999, Sheldon Hearn wrote:
Why do you need to kill and restart it? Doing a HUP is the standard way to
cause reprocessing of config files, so why has this changed?
It hasn't, but inetd in 3.2-RELEASE had a bug that scrambled its configuration
on HUP. Naturally, it's been
On Mon, 13 Sep 1999 12:33:27 MST, Kris Kennaway wrote:
Why do you need to kill and restart it? Doing a HUP is the standard way to
cause reprocessing of config files, so why has this changed?
It hasn't, but inetd in 3.2-RELEASE had a bug that scrambled its configuration
on HUP. Naturally,
On 13-Sep-99 Sheldon Hearn wrote:
That's why it's not "working". Uncomment the ntalkd line in
/etc/inetd.conf, kill and restart inetd. If you're using 3.2-RELEASE,
you really do need to kill and restart inetd -- don't just HUP it.
Why is restarting it necessary? The man page doesn't say
