Re: tracking down the cause of an entry in syslog?

To: debian users <debian-user@lists.debian.org>
Subject: Re: tracking down the cause of an entry in syslog?
From: "Eric G. Miller" <egm2@jps.net>
Date: Sat, 23 Jun 2001 11:05:45 -0700
Message-id: <[🔎] 20010623110545.A3713@calico.local>
Mail-followup-to: "Eric G. Miller" <egm2@jps.net>, debian users <debian-user@lists.debian.org>
In-reply-to: <[🔎] 20010623030839.T27373@plato.local.lan>
References: <[🔎] 15DYVZ-1gf-00@j001.june.home> <[🔎] 20010622213353.A1496@calico.local> <[🔎] 20010623014152.B31539@godzillah> <hmh@debian.org> <[🔎] 15DhB1-2Zy-00@j001.june.home> <[🔎] 20010623074531.A24237@godzillah> <[🔎] 20010623030839.T27373@plato.local.lan>

My mistake.  I assumed it was fetchmail, since ident requests by
fetchmail occur in conjunction with these bad port messages...

-- 
Eric G. Miller <egm2@jps.net>

Reply to:

References:
- tracking down the cause of an entry in syslog?
  - From: Paul Wright <paul@cvanet.com>
- Re: tracking down the cause of an entry in syslog?
  - From: "Eric G. Miller" <egm2@jps.net>
- Re: tracking down the cause of an entry in syslog?
  - From: Henrique de Moraes Holschuh <hmh@debian.org>
- Re: tracking down the cause of an entry in syslog?
  - From: Paul Wright <paul@cvanet.com>
- Re: tracking down the cause of an entry in syslog?
  - From: Henrique de Moraes Holschuh <hmh@debian.org>
- Re: tracking down the cause of an entry in syslog?
  - From: Ethan Benson <erbenson@alaska.net>

Prev by Date: Re: Slink->Potato, Perl version
Next by Date: Re: integrity check?
Previous by thread: Re: tracking down the cause of an entry in syslog?
Next by thread: System Backup to CD
Index(es):
- Date
- Thread