On 2007-08-30 21:12:15 -0400, Charlie Brady wrote: > On Thu, 30 Aug 2007, Peter J. Holzer wrote: > >On 2007-08-29 17:50:28 -0400, Charlie Brady wrote: > >>A four-tuple identifying the TCP connection also identifies the server. > > > >Right. And the tuple must not be reused for some time (2*MSL or 4 minutes > >according to RFC 793), so you don't even need a high resolution timer. > > Indeed. > > >However, what if there is no TCP connection yet? For example, in > >forkserver, the plugins are loaded before the first connection is > >accepted and you want to log a failure to load one of them (or the > >plugins may want to log something in their register method). > > I consider that to be a different issue. Log messages at that stage aren't > related to and don't need to be correlated with an email message.
Right, but we still want to log them and find out what logged them.
>
> >You could just fill the remote part with zeros, but you can have
> >multiple processes listening on the same port and you can't distinguish
> >them in this case.
>
> You can't have multiple processes bound to the same
> local_IP/local_port,
Sure I can:
habanero:~ 9:50 101# lsof -i :80 | grep LISTEN
httpd 9875 root 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9946 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9967 root 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9970 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9974 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9977 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9980 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9981 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 9991 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 10397 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 10400 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 10403 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 10790 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 11176 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 11728 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14183 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14186 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14187 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14194 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14195 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14198 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14201 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
httpd 14207 oraport 27u IPv4 81804443 TCP *:http (LISTEN)
The httpd in question is an Apache btw, so I'd expect an Apache::Qpsmtpd
installation to look similar.
> so you could distinguish hosts and processes by filling in the local
> part of the four-tuple.
That's what I meant with "fill the remote part with zeros".
hp
--
_ | Peter J. Holzer | I know I'd be respectful of a pirate
|_|_) | Sysadmin WSR | with an emu on his shoulder.
| | | [EMAIL PROTECTED] |
__/ | http://www.hjp.at/ | -- Sam in "Freefall"
signature.asc
Description: Digital signature
