Hugo Villeneuve <[EMAIL PROTECTED]> wrote:
> Thanks Mark,
> Adding SHELL = /bin/sh to my mailman crontab solved my problem. I think
> it would be a good idea to add a note to the Mailman installation manual for
> people using fcron instead of cron. I have attached my complete crontab as a
Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Well, I don't use fcron so I don't know for sure, but looking at the
> various manpages leads me to think that the shell= setting in the
> fcron config file is only a default if the shell is not otherwise
> specified.
>
> man 5 fcrontab
>
> says
>
> Whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hugo Villeneuve wrote:
> On Sun, 18 Dec 2005 14:15:46 -0800
> Mark Sapiro <[EMAIL PROTECTED]> wrote:
>> fcron by default runs commands using the user's login shell from
>> /etc/passwd. Thus you have to either specify a valid shell in
>> /etc/passwd or
Hugo Villeneuve wrote:
>
>In the fcron configuration file, I have already this line for the shell:
> shell = /bin/sh
Well, I don't use fcron so I don't know for sure, but looking at the
various manpages leads me to think that the shell= setting in the
fcron config file is only a default if th
On Sun, 2005-12-18 at 15:20 -0800, Mark Sapiro wrote:
> Terry Grey wrote:
> >
> >We have recently upgraded to ver 2.1.6 and are currently experiencing a
> >problem with pending moderator requests. The emails are sent to the list
> >admins correctly but when accessing the admindb web page there is t
On Sun, 18 Dec 2005 14:15:46 -0800
Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Hugo Villeneuve wrote:
> >
> > I'm using fcron to schedule the mailman jobs. I configured fcron to run
> > the mailman jobs as the mailman user (fcrontab -u mailman...). I also
> > created the mailman user with no lo
Terry Grey wrote:
>
>We have recently upgraded to ver 2.1.6 and are currently experiencing a
>problem with pending moderator requests. The emails are sent to the list
>admins correctly but when accessing the admindb web page there is the
>message "Click on the message number to view the individual
Hugo Villeneuve wrote:
>
> I'm using fcron to schedule the mailman jobs. I configured fcron to run
> the mailman jobs as the mailman user (fcrontab -u mailman...). I also created
> the mailman user with no login shell (/bin/false), similar to what is
> suggested in the mailman installation
Hi,
I'm using fcron to schedule the mailman jobs. I configured fcron to run
the mailman jobs as the mailman user (fcrontab -u mailman...). I also created
the mailman user with no login shell (/bin/false), similar to what is suggested
in the mailman installation manual.
When the
Hi. I've solved this. I seemed to have had two copies of the CGI programs,
one in /usr/share/mailman and the other in /var/www/mailman - I guess one
was from a botched install. Once I made sure mmsearch and htdig were in the
right place, all was well. I must have done the htdig configure with t
John Poltorak wrote:
>On Sat, Dec 17, 2005 at 10:18:27AM -0800, Mark Sapiro wrote:
>>
>> All confirmations including confirmation (acceptance) of invitations
>> expire as set by the Defaults.py/mm_cfg.py setting
>> PENDING_REQUEST_LIFE which defaults to 3 days.
>
>Can this default be set after th
On Sat, Dec 17, 2005 at 10:18:27AM -0800, Mark Sapiro wrote:
> Brad Knowles wrote:
>
> >At 11:21 AM + 2005-12-16, John Poltorak wrote:
> >
> >> When an invitation is sent out from a mailing list for someone to join,
> >> how long is it before it expires?
> >
> > I'm pretty sure that ther
12 matches
Mail list logo
