[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: diffrent behaviour of mailq, and some other stuff
On Fri, Nov 12, 1999 at 05:14:58PM -0000, Tomasz Bojakowski wrote:
> Well, it may work, however it seem's that mailq is broken either.
> I've DISABLED second process of scheduler and roiuter (that which was locking
> diffrent postoffice dir). So now zmailer runs like in normal enviroment.
Right, I disabled my experimental "mailqv2" code, and then I saw
the nothingness myself too. Now it is cured.
> [root@devil|/usr/local/src/zmailer/scheduler]# ./mailq
> ./mailq: connect failed to 127.0.0.1
> ./mailq: connect: Connection refused
> ./mailq: unable to contact scheduler on localhost
It takes a few seconds before socket is activated, perhaps that
is why you got that ?
> hum ? strange... or is new mailq by default accessing UNIX-domain sockets ?
> (I'm not too familiar with this subject, still trying to read sth. about
> unix-domain sockets)
No, TCP/174 (a.k.a. "mailq") is the default, but it doesn't
become activated immediately.
> Tomasz Bojakowski
> || tel. +48603081163 , email@example.com , firstname.lastname@example.org ||
/Matti Aarnio <email@example.com>