Re: That nsswitch.conf problem
On Sat, 15 Nov 1997, Karl M. Hegbloom wrote:
> >>>>> "Mike" == Mike Orr <email@example.com> writes:
> Mike> If there is anyone else besides Roman for whom this solution
> Mike> has *not* worked, please email me.
> I was having trouble logging in one day after an upgrade, and went to
> irc.debian.org #debian and asked... I was told to check
> nsswitch.conf, and to see whether `dns' was on the networks line.
> Turns out that had nothing to do with why I couldn't log in.
> What was going on, I'm not sure. What I do know is that there was a
> `fetchmail' running that had, with `ps -wauxf', a `formail -s
> procmail' and a `procmail' hanging from it. The `tleds' where not
> blinking, and I was seeing no incoming mail, which I log from
> .procmailrc to /dev/xconsole where I can watch it come in.
> So, can someone tell me, in 10 minutes or less, what was going on and
> why that happened?
If it makes you feel any better, you're not alone. :(
After I upgraded something fetchmail(3.8.0) just stopped working here
-- it goes throug USER/PASS/STAT and then hangs on RETR 1.
No smtp/pop packets come from pop server according to tcpdump.
 I grepped /var/lib/dpkg/info to see which files have been created in
the last couple of days (anyone can tell me how to list packages upgraded
in the last couple of days?) and none of them looked suspicious. I don't
see how tcl-8.0 or mount could affect fetchmail/xinetd/qmail...
 I know about fetchmail --mda. First, fetchmail "is designed to
deliver to port 25", according to readme and if you have to resort to
"--mda" then fetchmail simply does not work as advertised, full stop.
Second, fetchmail --mda doesn't work with qmail all that well.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .