On a newly installed system, I'm getting error messages from vixie cron
about PAM authentication errors:
Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication failure)
Feb 25 09:52:01 alpha crond[23085]: (root) FAILED to authorize user with PAM
(Authentication failure)
Feb 25
On Tue, Feb 25, 2014 at 9:29 PM, Grant Edwards grant.b.edwa...@gmail.comwrote:
On a newly installed system, I'm getting error messages from vixie cron
about PAM authentication errors:
Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication
failure)
Feb 25 09:52:01 alpha
On Friday 16 April 2010 22:25:47 Alan McKinnon wrote:
On Friday 16 April 2010 20:29:27 Dale wrote:
Alan McKinnon wrote:
On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
I apologise if this has come twice, it didn't appear to post correctly
first time, not even on the archives.
On Sat, 17 Apr 2010 11:00:02 +0200, Mick wrote about Re: [gentoo-user]
vixie-cron keeps stopping:
On Friday 16 April 2010 22:25:47 Alan McKinnon wrote:
[snip]
... and as for vixie-cron: When software doesn't act like it's
supposed to, breaks in horrible ways without giving me any clue
(like
On Saturday 17 April 2010 10:47:15 Mick wrote:
On Friday 16 April 2010 22:25:47 Alan McKinnon wrote:
On Friday 16 April 2010 20:29:27 Dale wrote:
Alan McKinnon wrote:
On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
I apologise if this has come twice, it didn't appear to post
On 4/15/2010 1:20 AM, Alan McKinnon wrote:
On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
I apologise if this has come twice, it didn't appear to post correctly
first time, not even on the archives.
Its been happening for a while but I haven't got round to find out why, but
every so
Alan McKinnon wrote:
On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
I apologise if this has come twice, it didn't appear to post correctly
first time, not even on the archives.
Its been happening for a while but I haven't got round to find out why, but
every so often (anything
On Friday 16 April 2010 19:22:42 kashani wrote:
On 4/15/2010 1:20 AM, Alan McKinnon wrote:
On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
I apologise if this has come twice, it didn't appear to post correctly
first time, not even on the archives.
Its been happening for a while
On Friday 16 April 2010 20:29:27 Dale wrote:
Alan McKinnon wrote:
On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
I apologise if this has come twice, it didn't appear to post correctly
first time, not even on the archives.
Its been happening for a while but I haven't got round
On Thu, 15 Apr 2010 01:36:38 +0100, Matt Harrison wrote:
Its been happening for a while but I haven't got round to find out why,
but every so often (anything between a week or an hour) vixie-cron just
stops. There's nothing in the logs, the service just stops.
Try running it from a terminal
On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
I apologise if this has come twice, it didn't appear to post correctly
first time, not even on the archives.
Its been happening for a while but I haven't got round to find out why, but
every so often (anything between a week or an hour)
On 15/04/2010 09:20, Alan McKinnon wrote:
You probably don't want to hear this, but:
vixie-cron is problematic in the extreme. I have endless hassle with it's
weird behaviours.
Use a different cron daemon.
I don't mind hearing this :) I only use vixie-cron as that is what I
started
Its been happening for a while but I haven't got round to find out why, but
every so
often (anything between a week or an hour) vixie-cron just stops. There's
nothing in
the logs, the service just stops.
I have no idea where to start looking for a culprit so I'm hoping someone here
has
some
I apologise if this has come twice, it didn't appear to post correctly first
time, not
even on the archives.
Its been happening for a while but I haven't got round to find out why, but
every so
often (anything between a week or an hour) vixie-cron just stops. There's
nothing in
the logs, the
On Wed, Apr 14, 2010 at 5:58 PM, Matt Harrison
iwasinnamuk...@genestate.com wrote:
I apologise if this has come twice, it didn't appear to post correctly first
time, not
even on the archives.
Its been happening for a while but I haven't got round to find out why, but
every so
often
I've set the MAILTO env variable in my crontab, but vixie-cron
still isn't sending e-mails. I've verfied that I'm able to
send email with /usr/sbin/sendmail (both with and without -t).
I re-emerged vixie-cron with the debug USE flag, but it didn't
seem to produce any debug info that I can find
Hi,
Thank you very much. But how I can use @reboot? It
might be good if I just run fetchmail once after rebooting.
--
Wish you well!
Teng Wang
--
gentoo-user@lists.gentoo.org mailing list
On Tuesday 10 June 2008, Teng Wang wrote:
Hi,
Thank you very much. But how I can use @reboot? It
might be good if I just run fetchmail once after rebooting.
I don't understand your question, the man page clearly tells you how to
use it:
Replace the first five columns in a crontab file with
On Sat, Jun 7, 2008 at 1:12 AM, Teng Wang [EMAIL PROTECTED] wrote:
Hi there,
I am using vixie cron to maintain my scheduled
jobs. Everything is just fine other than one. I find that
when I use, for example, 0 * * * * /usr/bin/eix-sync to
update the portage everyday, the cron works without
Hi there,
I am using vixie cron to maintain my scheduled
jobs. Everything is just fine other than one. I find that
when I use, for example, 0 * * * * /usr/bin/eix-sync to
update the portage everyday, the cron works without any
problem. But I was told by manpage I could still use @daily
instead.
On Sat, 10 Nov 2007 02:15:44 -0600
Teng Wang [EMAIL PROTECTED] wrote:
I see, thank you!
Do I need add news to /etc/cron.allow?
possibly.
--
[EMAIL PROTECTED] mailing list
hey all,
Recently, I set up a local news server and want to fetch news by using
vixie cron. For security, I want to drop root to news ( only news and
root can run fetchnews). So I add one line in crontab by using
crontab -e:
*/5 * * * * news fetchnews
Actually, I just follow the
I see, thank you!
Do I need add news to /etc/cron.allow?
--
[EMAIL PROTECTED] mailing list
hey all,
Recently, I set up a local news server and want to fetch news by using
vixie cron. For security, I want to drop root to news ( only news and
root can run fetchnews). So I add one line in crontab by using
crontab -e:
*/5 * * * * news fetchnews
Actually, I just follow the examples from
sean wrote:
How is vixie-cron setup to accept remote connections?
Thanks
Sean
Forget this question, made a mistake.
--
[EMAIL PROTECTED] mailing list
:)
I've got another question. I recognized that vixie-cron stopped working
after the last reboot of my server. I
On Saturday 03 November 2007, Zimmerling, Alexander wrote:
sean wrote:
How is vixie-cron setup to accept remote connections?
Thanks
Sean
Forget this question, made a mistake.
--
[EMAIL PROTECTED] mailing list
:)
I've got another question. I recognized
On Saturday 03 November 2007, Zimmerling, Alexander wrote:
sean wrote:
How is vixie-cron setup to accept remote connections?
Thanks
Sean
Forget this question, made a mistake.
--
[EMAIL PROTECTED] mailing list
:)
I've got another question. I recognized
How is vixie-cron setup to accept remote connections?
Thanks
Sean
--
[EMAIL PROTECTED] mailing list
On Friday 02 November 2007, sean wrote:
How is vixie-cron setup to accept remote connections?
Eh? Why would a cron daemon need to accept connections, what does that even
mean in the context of cron?
--
[EMAIL PROTECTED] mailing list
sean wrote:
How is vixie-cron setup to accept remote connections?
Thanks
Sean
Forget this question, made a mistake.
--
[EMAIL PROTECTED] mailing list
Hi Richard, thank you for your reply, I will look at these more closely as for
the moment I have not set a user specific cron, I am just using the root to run
these.
All I did was follow the tutorial, perhaps I have missed some points ;(
Cheers
Norman
Richard Fish [EMAIL PROTECTED] wrote: On
On 1/5/07, norman [EMAIL PROTECTED] wrote:
Hello,
I am running vixie-cron, but am unable to figure out what this is all about,
I have followed the
http://www.gentoo.org/doc/en/cron-guide.xml
But on the report email, I only get on the email, the following:
/bin/sh: root: command not found
On 9/15/06, David Grant [EMAIL PROTECTED] wrote:
Forget it, I gave up on ssmtp as it is the problem. I've now gone to postfix
and it is so much easier. Setting up postfix involed 3 simple steps. Setting
relayhost in /etc/postfix/main.cf and creating .forward files in root and
normal user
Cron is sending out an email for jobs run as user root, but not for cron jobs run as my normal user? Yet the funny thing is, when cron runs jobs as normal user, it still actually sends the mail to root (see /etc/crontab). And on the command line, I see the same thing either way:
Sep 14 14:43:01
On Thu, 14 Sep 2006 14:43:30 -0700, David Grant wrote:
Cron is sending out an email for jobs run as user root, but not for cron
jobs run as my normal user? Yet the funny thing is, when cron runs jobs
as normal user, it still actually sends the mail to root
(see /etc/crontab).
You seem to be
On 9/14/06, Neil Bothwick [EMAIL PROTECTED] wrote:
On Thu, 14 Sep 2006 14:43:30 -0700, David Grant wrote: Cron is sending out an email for jobs run as user root, but not for cron jobs run as my normal user? Yet the funny thing is, when cron runs jobs
as normal user, it still actually sends the
On 9/14/06, David Grant [EMAIL PROTECTED] wrote:
On 9/14/06, Neil Bothwick
[EMAIL PROTECTED] wrote:
On Thu, 14 Sep 2006 14:43:30 -0700, David Grant wrote: Cron is sending out an email for jobs run as user root, but not for cron jobs run as my normal user? Yet the funny thing is, when cron runs
On 9/14/06, David Grant [EMAIL PROTECTED]
wrote:
Hmm, it turns out that setting MAILTO=root in my own user's crontab makes it send mail. MAILTO=root is already in /etc/cron/crontab by the way so this is all very strange.
I tried setting MAILTO=david and that didn't work. I decided ssmtp might
The cron manpage says that /etc/crontab should have mode 0600.
However, it is installed with 0644.
A /etc/cron.deny is installed without any users in it which
means (according to crontab(1)) that all users are allowed
to work with crontab.
However, /usr/bin/crontab has mode 4710 which means that
Hans de Hartog wrote:
The cron manpage says that /etc/crontab should have mode 0600.
However, it is installed with 0644.
A /etc/cron.deny is installed without any users in it which
means (according to crontab(1)) that all users are allowed
to work with crontab.
However, /usr/bin/crontab has mode
40 matches
Mail list logo
