Re: missing subfolders in /tmp/.policyd-weight
oh, alles klar. Ich dachte nur weil der autor auf der homepage schreibt das hier nicht viel los wäre. ok, ich ändere nun mein setup ein bisschen ab, ist wohl das beste. ich entferne den kram aus der master und starte den policyd-weight als separaten daemon. in der main.cf notiere ich dann check_policy_service inet:127.0.0.1:12525 so wie vorgesehen. nur beim stop -> start hab ich die erfahrung gemacht das er da ab und zu hängt. dies kann ich aber umgehen wenn ich /tmp/.policyd-weight entferne nach dem stop. ich baus mal so in das postfix startscript ein, wird das beste sein. mal sehen vielen dank andre - Original Message - From: "Daniel Hackenberg" <[EMAIL PROTECTED]> To: "Andre Hübner" <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2008 2:02 PM Subject: Re: missing subfolders in /tmp/.policyd-weight So inaktiv ist die Liste gar nicht. Das siehst du, wenn du mal in das Listen-Archiv unter http://news.gmane.org/gmane.mail.postfix.policyd%2dweight schaust. Und da gibt es dann Einträge wie diesen hier http://article.gmane.org/gmane.mail.postfix.policyd-weight/817 oder diesen hier http://article.gmane.org/gmane.mail.postfix.policyd-weight/831 die irgendwie ganz ähnlich wie dein Problem klingen... Daniel 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-pdwunix - 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, 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. 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? What could be the reason to do start the policyd-weight from master.cf? Thank you Andre Policyd-weight Mailinglist - http://www.policyd-weight.org/ Policyd-weight Mailinglist - http://www.policyd-weight.org/
Re: missing subfolders in /tmp/.policyd-weight
monit is good for that too. - Whit On Tue, Apr 01, 2008 at 03:02:26PM +0200, Robert Felber wrote: > > 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. Policyd-weight Mailinglist - http://www.policyd-weight.org/
Re: missing subfolders in /tmp/.policyd-weight
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-pdwunix - 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, 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/
missing subfolders in /tmp/.policyd-weight
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-pdwunix - 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, 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. 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? What could be the reason to do start the policyd-weight from master.cf? Thank you Andre Policyd-weight Mailinglist - http://www.policyd-weight.org/
