policyd-weight init.d/script needs 1 fix
Package: policyd-weight Version: 0.1.14.5-1 Distribution: Debian Testing (Lenny) If you do not kill the cache instance, when you (in Debian) /etc/init.d/policyd-weight stop, it only stops the master/child (but not the cache) process. echo -n Stopping $DESC: + # kill cache instance first. +$DAEMON -k $DAEMON $DAEMON_OPTS stop echo $NAME. ;; Policyd-weight Mailinglist - http://www.policyd-weight.org/
Re: RBL-based greylisting using Policyd-weight and Postgrey
On Wed, Jan 16, 2008 at 06:09:20PM +0100, fili wrote: Ok, a bug. Fixing appears troublesome (breaks lowest-resource-usage-policy). Not certain whether requests which will be answered with 'rc:' should generally not be cached (this wouldn't break cache-resources). $CACHESIZE=0; Thanks Rovert, I've got it up and running now using $CACHESIZE=0; Do you think that no-caching might result in higher loads on a mail-heavy server? Not load, but more smtpd processes waiting for a polw reply. I've read the release info of 0.1.14 beta-14, specificly: results with 'rc:' as action are not cached Is it useful for my current setup to update? Useful yes, required, not really. And should I then change $CACHESIZE back to the default value? You can delete it (with the latest version). On a different note, wouldn't it be a good idea to introduce a variable like: $BLOCK_RETRY_TTL = 30; 30 being the seconds in which retries will be temporarily blocked. If this value is set to 0, then Policyd-weight won't block retries at all. This is the job of $NTTL and $NTIME in concert $NTTL (default: 1) The client is penalized for that many retries. $NTIME (default: 30) The $NTTL counter will only be decremented if the client waits at least $NTIME seconds. -- Robert Felber (PGP: 896CF30B) Munich, Germany Policyd-weight Mailinglist - http://www.policyd-weight.org/
Re: Bug#461124: policyd-weight init.d/script needs 1 fix
Hi Justin, On Wednesday 16 January 2008 19:39, Justin Piszcz wrote: Package: policyd-weight Version: 0.1.14.5-1 Distribution: Debian Testing (Lenny) If you do not kill the cache instance, when you (in Debian) /etc/init.d/policyd-weight stop, it only stops the master/child (but not the cache) process. echo -n Stopping $DESC: + # kill cache instance first. +$DAEMON -k $DAEMON $DAEMON_OPTS stop echo $NAME. ;; what if I don't want to kill the cache and only stop the daemon (for what reason ever)? With kind regards, Jan. -- Never write mail to [EMAIL PROTECTED], you have been warned! -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-- pgparX1Gsx5yE.pgp Description: PGP signature
Re: Bug#461124: policyd-weight init.d/script needs 1 fix
On Wed, Jan 16, 2008 at 09:36:30PM +0100, Jan Wagner wrote: On Wednesday 16 January 2008 20:47, Justin Piszcz wrote: Perhaps per-Robert, Make one for the cache, one for the daemon? e.g., when one 'stops' a daemon, shouldn't it kill all relevant processes it created? what if anybody comes to the idea to stop the cache via initscript, but don't stop the daemon? In this case it should be ensured, that the cache is starting or is started, when the daemon starts. I guess thats most of the users are confused by 2 init scripts and will not use it in the correct way. For example stoping the cache while the daemon runs or things like that. I would prefer to echo a hint when stoping/restarting the daemon, how to stop the cache. Any invents? Well to avoid discussions about correctness I'd be okay if we say rc.d/policyd-weight stop|start|restart|dstop|drestart stop|start|restart - affects all (cache, daemon) dstop|drestart - affects only daemon In the end, everyone expects the cache to be killed, too. Those that have read an updated documentation know, that the daemon can also be stop/[re]started by just issuing /usr/sbin/policyd-weight stop|start or using the appropriate init params if they are used to manage everything via init scripts. I would count it as collateral damage if some users frequently purge the cache. -- Robert Felber (PGP: 896CF30B) Munich, Germany Policyd-weight Mailinglist - http://www.policyd-weight.org/
Re: Bug#461124: policyd-weight init.d/script needs 1 fix
On Wed, 16 Jan 2008, Jan Wagner wrote: On Wednesday 16 January 2008 20:47, Justin Piszcz wrote: Perhaps per-Robert, Make one for the cache, one for the daemon? e.g., when one 'stops' a daemon, shouldn't it kill all relevant processes it created? what if anybody comes to the idea to stop the cache via initscript, but don't stop the daemon? In this case it should be ensured, that the cache is starting or is started, when the daemon starts. I guess thats most of the users are confused by 2 init scripts and will not use it in the correct way. For example stoping the cache while the daemon runs or things like that. I would prefer to echo a hint when stoping/restarting the daemon, how to stop the cache. Any invents? With kind regards, Jan. -- Hmm good question, perhaps make 'stop' to fully stop the service but a second stop if you want to keep the cache running? I am not sure what is the best recommended method that everyone would agree with. Justin. Policyd-weight Mailinglist - http://www.policyd-weight.org/
Re: Bug#461124: policyd-weight init.d/script needs 1 fix
On Wednesday 16 January 2008 21:58, Robert Felber wrote: Well to avoid discussions about correctness I'd be okay if we say rc.d/policyd-weight stop|start|restart|dstop|drestart stop|start|restart - affects all (cache, daemon) dstop|drestart - affects only daemon I would turn it around and say: stop|restart- affects only daemon start|cstop|crestart- affects all (cache, daemon) This has the advantage that the actual behavior isn't changed and that people not knowing what they are doing, don't wipe the cache by default. Adding a hint (echo to stdout) on stop|restart how to kill the cache should also enlighten ppl. With kind regards, Jan. -- Never write mail to [EMAIL PROTECTED], you have been warned! -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-- pgpusqdF3ZqnK.pgp Description: PGP signature
