outgoing mail STOPPED.

Matthew Seaman m.seaman at infracaninophile.co.uk
Mon Jan 7 03:13:51 PST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Gary Kline wrote:

>> 	Then I checked my /etc/namedb/s/db.thought.org to see id anything there 
>> 	could conceivably be hanging port 25.  Zip.  (I still updated the
>> 	date and re-exed. I checked with ps and grep to find something new:

The best way to check for any processes listening on port 25 is:

% sockstat | grep :25 
root     sendmail   1193  3  tcp4   81.187.76.162:25      *:*
root     sendmail   1193  5  tcp4   127.0.0.1:25          *:*
root     sendmail   1193  6  tcp6   ::1:25                *:*
root     sendmail   1193  7  tcp6   2001:8b0:151:1:240:5ff:fea5:8db7:25*:*

>>                    ~
>> 624  ??  Ss     0:01.16 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/r
>> p0 0:27 <sage> [5005]
> 
>> 	In theory I know pretty much what bind9does, &c; but why this
>> 	change?  (Part of my gnome (2.20) is missing so I cannot max
>> 	enlarge the konsole; ps -alx does not wrap so I cant see the 
>> 	entire string.)  I can pimg ns1.thought.org--obviously.  But if you
>> 	see anything here,  Matthew, would you please let me know?

To get ps output without truncation, simply add 'ww' to the flags --
one 'w' gives you a 132 column output (shades of those old fan-fold line
printer TTYs there) and two (or more) 'w's gives you unlimited width:

# ps -alx | grep /usr/sbin/s
    0   689     1   0  44  0  3188  1240 select Ss    ??    0:07.28 /usr/sbin/s
    0  1188     1   0  44  0  5640  3356 select Is    ??    0:00.02 /usr/sbin/s
# ps -alxww | grep /usr/sbin/s
    0   689     1   0  44  0  3188  1240 -      Rs    ??    0:07.29 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -a 81.187.76.161/32:4096 -l /var/named/var/run/log
    0  1188     1   0  44  0  5640  3356 select Is    ??    0:00.02 /usr/sbin/sshd
 1001 16014  1376   0  44  0   380   260 -      R+    p0    0:00.00 grep /usr/sbin/s

As for the presence of '-l /var/named/var/run/log' -- that's added
to the syslogd flags automatically by the /etc/rc.d/syslogd startup
script[*] if you're running named chrooted (which is the default). This
means that syslogd can log the items outside the chroot that are generated
by named within it.  You should see output from named in /var/log/all.log
- -- precisely what you see depends entirely on the logging configuration
in named.conf.

	Cheers,

	Matthew

[*] The reason I have it twice is that a long time ago I'd also added
it to syslogd_flags manually, something I shall correct imminently.

- -- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                  Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHgglp8Mjk52CukIwRCMTeAJ9U/iicerUyzugUEucgZ1fFvavB7ACeNLkM
/Go2XMJctLl+Ci9w3RrjxeM=
=LbnH
-----END PGP SIGNATURE-----


More information about the freebsd-questions mailing list