On Tue, Apr 01, 2008 at 01:27:07PM +0200, Andre Hübner wrote: > Hi List, > > i hope there is enough traffic here to get answers. ;) > > Im updateing my postfix-configuration to the new policyd-weight Version: > 0.1.14 > beta-17 > > Only difference to ./policyd-weight defaults is: > > $GROUP = "nogroup"; > > policyd-weight.conf is in /etc/ > > I do not start policyd-weight by ./policyd-weight start, i have this in my > master.cf: > > policy-pdw unix - n n - - spawn user=polw > argv=/usr/lib/postfix/policyd-weight > > i cannot say the reason why this is made that way, this was made by other > people > > policyd-weight is running and gives a correct checkresult, but between the > checks are also warnings in the log. > > > Apr 1 12:41:46 servername postfix/policyd-weight[8958]: warning: > cache_query: > $csock couln't be created: connect: No such file or directory, calling > spawn_cache > () > Apr 1 12:41:46 servername postfix/policyd-weight[8981]: warning: cache: err: > cache: chdir /tmp/.policyd-weight/: No such file or directory at > /usr/lib/postfix/p > olicyd-weight line 2948, <STDIN> line 120. > > > I dont know what to do. > > /tmp/.policyd-weight is existing. It is recursivly chowned to polw.nogroup > and > its chmod is 700 > > What could be wrong? > > If i start policyd-weight with ./policyd-weight start and stopping it again > after incoming mails no warnings are visible and /tmp/.policyd-weight has > cores/master cores/cache > > Is there a way to create this folders in correct way without starting it > directly.
Yes one someone needs to fix policyd-weight which creates this directories also in non-damon mode. Policyd-weight itself doesn't have a nice routine for easily creating directory X with correct perms, owners and symlink checks. > I could do this in my postfix rpm or in postfix startscript, but i > would prefer solution within the script itself. Or is it better to start it > like author is recommend? I would say 'policyd-weight start' is better. > What could be the reason to do start the > policyd-weight from master.cf? Probably that it promises some failover-redundancy because postfix would start the program for each smtpd session. If policyd-weight crashes, it would be re-called the next time a smtpd session is made. However, if you fear that policyd-weight (or any other daemon for that matter) crashes and want to restart it automatically you may want to have a look at runit [1] or daemontools [2]. Personally I use none of those as I rather have crashed services than undiscovered problems. 1: http://smarden.org/runit/ 2: http://cr.yp.to/daemontools.html -- Robert Felber (PGP: 896CF30B) Munich, Germany ____________________________________________________________ Policyd-weight Mailinglist - http://www.policyd-weight.org/
