Re: unreachable check_policy_service
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. :-) With kind regards, Jan. -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT d-- s+: a- C+++ UL P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++ --END GEEK CODE BLOCK-- pgpV0ZBMmR0WI.pgp Description: PGP signature
Re: unreachable check_policy_service
On Monday 18 September 2006 16:01, Robert Felber wrote: 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) Normaly I use ps-watcher (http://ps-watcher.sourceforge.net/) :-) But this wouldn´t help if there is policyd-weight running on a dedicated server and this one is unreachable (crash/hardware failure/network trouble/ ...) Thanks and with kind regards, Jan. -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT d-- s+: a- C+++ UL P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++ --END GEEK CODE BLOCK-- pgpz7VjkCT9jZ.pgp Description: PGP signature
Re: unreachable check_policy_service
On Mon, Sep 18, 2006 at 04:19:01PM +0200, Jan Wagner wrote: To make sure that policyd-weight always runs you could use some sort of daemon-tools (http://cr.yp.to/daemontools.html) Normaly I use ps-watcher (http://ps-watcher.sourceforge.net/) :-) But this wouldn?t help if there is policyd-weight running on a dedicated server and this one is unreachable (crash/hardware failure/network trouble/ ...) Indeed. This should be probably handled by postfix, meaning, that one should be able to decide whether to DUNNO the check_policy_service in case of connection problems. -- Robert Felber (PGP: 896CF30B) Munich, Germany Policyd-weight Mailinglist - http://www.policyd-weight.org/
