Re: [9fans] /sys/log/listen

[forsyth@caldo.demon.co.uk]

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

listen attempts to announce each name in /rc/bin/service (for the given protocol)
which in turn causes announce to translate them using cs(8), which fails for
25_block because that's neither a port number nor
is it assigned a port number by /lib/ndb/common.
that in turn is unsurprising because it's not supposed to be given a port number;
it looks like the name resulting from mv'ing tcp25 to render it unusable
but keeping the file contents available if needed later (as opposed to simply removing it).


[-- Attachment #2: Type: message/rfc822, Size: 2139 bytes --]

From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] /sys/log/listen
Date: Sun, 31 Dec 2000 12:02:36 -0500
Message-ID: <20001231110603.8BB30199D5@mail.cse.psu.edu>

I happened to look into my /sys/log/listen file and noticed alot
of entries. I wasn't expecting to see this because everything seems
to be working fine with my 'aux/listen tcp': I am able to send and
receive mail just fine.

Portion of entry:

localhostnl Dec 31 06:39:35 giving up on tcp!*!25_block: cs: can't translate address
localhostnl Dec 31 06:40:35 giving up on tcp!*!25_block: cs: can't translate address
localhostnl Dec 31 06:40:35 giving up on tcp!*!25_block: cs: can't translate address

For background, here is how I am set up.

	Standalone system
	After connecting to my ISP I run:
		ndb/dns -r
		aux/listen tcp
		ftpfs into my ISP's server
		run 'acme Mail'

Is this something I should ignore? I am really interested in fine tuning
this.

Bill