Re: [vps-mail] Sigh... more permissions problems

[Scott Wiersdorf <scottw@xxxxxxxxxxxx>]

On Fri, Apr 09, 2004 at 12:26:55PM -0700, Abigail Marshall wrote:
> Everything was going fine, until.....
> 
> I am running a routine via savelogs that rotates various log
> files each day via cron.
> 
> The problem occurs AFTER savelogs is run, when the log files
> that have been rotated are recreated. The problem has shown
> up with procmail.log and with a file I'll call
> user1.log, which is created by the .procmailrc for that
> specific user.

<snip>

> I suppose I can fix this with shell script after savelogs
> that runs these commands:
> 
> touch /var/log/procmail.log
> chmod 644 /var/log/procmail.log

savelogs can do this for you with a --postmovehook (or PostMoveHook
config option):

    PostMoveHook    chmod 644 /var/log/procmail.log

Also specify the --touch option or:

    Touch           yes

This should do what you want there.

> 2. The other error message looks like this:
> 
> cannot create /var/mail/archives/users/user1.backup: permission denied
> 
> The problem is this - some of the user .procmailrc files are
> configured to send a copy of email to a backup file, with a
> command like this:
> :0 c
> /var/mail/archives/users/user1.backup
> 
> (The idea is that backups are created for user email to
> protect against lost email, with savelogs implemented to
> rotate & discard older records)
> 
> For reasons I can't figure out, the system is now unable to
> create the new user1.backup after the first one has been
> rotated by savelogs.

I think this is the same thing as above; you'll need to touch the file
(--touch for savelogs) and either chown or chmod the file (or both)
so that it's writable by that user:

    Touch           yes
    PostMoveHook    chown username /var/mail/archives/users/user1.backup

or something like that.

Scott
-- 
Scott Wiersdorf
scottw@xxxxxxxxxxxx
======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).