On Mon, Sep 18, 2006 at 03:52:36PM +0200, Jan Wagner wrote: > On Monday 18 September 2006 15:49, Robert Felber wrote: > > Not that I know. But since it 4xx indicates a temporary failure the other > > client should retry. > > > > Question is, is this error permanent, or just temporary due to a > > restart/update? > > I tried only to check, what happens if policyd.weight is unavailable, so I > stopped the service. :-)
The same thing that happens if postfix is not available ;-) Well, basically that's what Rahul Dhesi was asking on the postfix-user list ([EMAIL PROTECTED]). If you want "trusted stability/availability" it would be required that postfix has some sort of fallback-mechanism, I don't see that in future. Another tcp/daemon would be prone to being temporary not available, too. However, the 4xx mechanism which postfix uses *should* work in most cases. To make sure that policyd-weight always runs you could use some sort of daemon-tools (http://cr.yp.to/daemontools.html) -- Robert Felber (PGP: 896CF30B) Munich, Germany ____________________________________________________________ Policyd-weight Mailinglist - http://www.policyd-weight.org/
