[Mailman-Users] mailman complaining about script permissions after running normally for a period...
Ezra Taylor
etaylor at amnh.org
Wed Mar 9 17:13:36 CET 2005
Something is changing the ownership of your files. The previous
responder is right, a cron or logrotate is doing this.
Ezra
Brad Knowles wrote:
> At 11:12 AM +0000 2005-03-04, it support wrote:
>
>> I've tracked down the problem to the ownership of the files are
>> changing.
>> No longer are they being owned by mailman, but by root. I can fix the
>> problem by resetting the ownership of the files to mailman and
>> re-running check_perms -f to fix any stray permissions, but its
>> frustrating for the list users who have to wait for this to be done.
>
>
> There's nothing within Mailman that would cause this kind of
> behaviour.
>
>> I've checked the cron scripts on the machine and can't see anything
>> that
>> would affect the files in that part of the file system.
>
>
> I don't know anything about your OS. I'd recommend you use the
> mailing lists, newsgroups, FAQs, etc... that are appropriate to what
> you're running.
>
> I can tell you that the problem may be a logfile rotation script,
> or some other sort of cron job, or maybe it's being run indirectly --
> some other cron job runs some other command which results in the kind
> of behaviour you're seeing.
>
>> Has anyone else seen this problem and do they know the cause of it?
>
>
> You could search the archives of the mailman-users mailing list,
> such as described at
> <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.018.htp>.
> I've heard of these kinds of problems before, but I don't know if they
> occurred on the same platform that you're running.
>
More information about the Mailman-Users
mailing list