procmail
[Top] [All Lists]

Q: When locking report looks different in the log

2001-12-12 09:04:37
Hello,

    [ First I apologize for my poor english ]
        
    I miss the lines about the lockfile in the log.  I see the locking
    reports just in cases when I send a message to /dev/null.  But, when
    I run the procmail from command line with same procmailrc, I see the
    locking report lines from all cases.     ((and do not see the
    "procmail: Assigning "PATH=..." line.))

    The lines that I see in log if runs command line and are missing in
    normal proccess are: (after "Executing...")

...
procmail: Matched "exe"
procmail: Match on "()\/(pif|scr|vbs|sbs|com|exe|bat)"
procmail: Executing " sed -e
"/^Content-.*\.$MATCH\>/s/\.$MATCH\>/_$MATCH/g" \
              -e     "/^begin\>.*\.$MATCH\>/s/\.$MATCH\>/_$MATCH/g" \
              -e "/^.*e*name=\".*\.$MATCH\>/s/\.$MATCH\>/_$MATCH/g""
procmail: Locking "/var/spool/mail/uuddii.lock"
procmail: Assigning "LASTFOLDER=/var/spool/mail/uuddii"
procmail: Opening "/var/spool/mail/uuddii"
procmail: Acquiring kernel-lock
procmail: Unlocking "/var/spool/mail/uuddii.lock"
...

    The last recipe in my procmailrc calls sed(1) filter, is
    my spool saved?  Do my users can sleep well? (!)

    Of course, if I add ":" to recipe which calls sed(1) it     reports
    the: "Extraneous locallockfile ignored"

    OS= Redhat 7.2  kernel= 2.4.9-0.5  Procmail= v3.22 2001/09/10
    Sendmail= 8.10.2

    Any idea?

Thenks
Udi

_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>