Quoting "Kenneth E. Lussier" [EMAIL PROTECTED]:
That's a really good question (and I wish I had an answer). I'm guessing
that `netstat` can somehow tell you what's listening on what ports. A
port-scanner will do the trick, too. But what did you mean when you said
" I lost tcpd/pop3d"? What is
Jamie Blondin wrote:
I always stayed away from the killall commands precisely because I read
that manpage. (I really don't ever want to be making that mistake when
on another platform). But, yes, killall is even easier.
The Tru64 man page for killall reads in part "When started by the
Excellent! I was just considering how to script it easily...
Thanks,
Jamie Blondin
When doing some shell programming before I've used:
`ps ax | grep 'regexp' | grep -v grep | awk '{print $1}'
| xargs kill
-SIGHUP
**
?
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Joshua S. Freeman | preferred email: [EMAIL PROTECTED]
pgp public key: finger [EMAIL PROTECTED]
http://www.threeofus.com
kill -HUP inetd's PID
"Joshua S. Freeman" wrote:
?
**
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
Did you make any changes to /etc/inetd.conf? Something else that you may
want to check is if there is any sort of active process that has the
ports that you are using bound (some IDS tools like portsentry will do
this if it is satrtedbefore inetd).
Kenny
"Joshua S. Freeman" wrote:
Thanks...
It's strange...
I didn't make any changes at all to etc/inetd.conf, and I'm not running
anything else on that port (110) afaik... anything else I should check?
how do i check if there's a port conflict just in case?
J.On Tue, 8 Feb 2000,
Kenneth E. Lussier wrote:
Did you make any changes to
That's a really good question (and I wish I had an answer). I'm guessing
that `netstat` can somehow tell you what's listening on what ports. A
port-scanner will do the trick, too. But what did you mean when you said
" I lost tcpd/pop3d"? What is happening? Can you connect to port 110 at
all (by
On Tue, 8 Feb 2000, Jamie Blondin wrote:
Even easier...Assuming your inetd keeps its pid in /var/run/inetd.pid (Most
boxes I've seen do.):
# kill -HUP `cat /var/run/inetd.pid`
Easier still:
# killall -HUP inetd
(But, to quote the manpage: Be warned that typing "killall name" may not
On Tue, 8 Feb 2000, Joshua S. Freeman wrote:
I didn't make any changes at all to etc/inetd.conf, and I'm not running
anything else on that port (110) afaik... anything else I should check?
What *did* you change? :-)
Check your system log files.
You can also try invoking "tcpd" and
On Tue, 8 Feb 2000, Kenneth E. Lussier wrote:
That's a really good question (and I wish I had an answer). I'm guessing
that `netstat` can somehow tell you what's listening on what ports. A
$ netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address
11 matches
Mail list logo
