Quoting Haines Brown (hai...@histomat.net):
> On Sun, Jul 19, 2015 at 10:25:38PM -0500, David Wright wrote:
> > Quoting Haines Brown (hai...@histomat.net):
> >
> > > But I did enable a cron log, which for some reason was disabled on my
> > > system. I'll have to wait a week to see what that log ha
On Sun, Jul 19, 2015 at 10:25:38PM -0500, David Wright wrote:
> Quoting Haines Brown (hai...@histomat.net):
>
> > But I did enable a cron log, which for some reason was disabled on my
> > system. I'll have to wait a week to see what that log has to say. I
> > don't know how to set its level, or if
Quoting Haines Brown (hai...@histomat.net):
> But I did enable a cron log, which for some reason was disabled on my
> system. I'll have to wait a week to see what that log has to say. I
> don't know how to set its level, or if enabling the cron log captures
> all message from the cron daemon.
Wel
Quoting Haines Brown (hai...@histomat.net):
> On Sun, Jul 12, 2015 at 06:33:40PM +, Dan Purgert wrote:
> > Perhaps "environment variable" was the wrong phrase. I've run into
> > issues with cron jobs if I don't have it calling #!/bin/bash at the top
> > (or #!/bin/[whatever]) ... running fro
Haines Brown wrote:
> This may be a FAQ, but it has me stumped. I try to do a weekly backup
> with this, but nothing happens, and there is nothing in syslog:
> # crontab -l
> 0 4 * * 0 /home/haines/scripts/backup
Is this the only line in that crontab?
The default Vixie-cron has the oddity
On Sun, Jul 12, 2015 at 06:33:40PM +, Dan Purgert wrote:
> Perhaps "environment variable" was the wrong phrase. I've run into
> issues with cron jobs if I don't have it calling #!/bin/bash at the top
> (or #!/bin/[whatever]) ... running from a local terminal doesn't catch it
> because "sh s
On Sun, Jul 12, 2015 at 01:37:12PM -0400, Miles Fidelman wrote:
> Dan Purgert wrote:
> It could also be as simple as a permissions issue.
>
> If your syslog isn't showing anything, you might want to push up
> your logging level.
Thanks Miles. I don't know how permissions might come in because the
On Sun, 12 Jul 2015 14:22:22 -0400, Haines Brown wrote:
> On Sun, Jul 12, 2015 at 05:11:21PM +, Dan Purgert wrote:
>> On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
>>
>> > This may be a FAQ, but it has me stumped. I try to do a weekly backup
>> > with this, but nothing happens, and
On Sun, Jul 12, 2015 at 05:11:21PM +, Dan Purgert wrote:
> On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
>
> > This may be a FAQ, but it has me stumped. I try to do a weekly backup
> > with this, but nothing happens, and there is nothing in syslog:
> >
> > # crontab -l 0 4 * * 0 /
Hi
On Sun, 2015-07-12 at 13:02 -0400, Haines Brown wrote:
> This may be a FAQ, but it has me stumped. I try to do a weekly backup
> with this, but nothing happens, and there is nothing in syslog:
>
> # crontab -l
> 0 4 * * 0 /home/haines/scripts/backup
>
> I can run the script manually with
Dan Purgert wrote:
On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
This may be a FAQ, but it has me stumped. I try to do a weekly backup
with this, but nothing happens, and there is nothing in syslog:
# crontab -l 0 4 * * 0 /home/haines/scripts/backup
I can run the script manually
On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
> This may be a FAQ, but it has me stumped. I try to do a weekly backup
> with this, but nothing happens, and there is nothing in syslog:
>
> # crontab -l 0 4 * * 0 /home/haines/scripts/backup
>
> I can run the script manually with # /hom
This may be a FAQ, but it has me stumped. I try to do a weekly backup
with this, but nothing happens, and there is nothing in syslog:
# crontab -l
0 4 * * 0 /home/haines/scripts/backup
I can run the script manually with # /home/haines/scripts/backup.
Cron daemon is running:
$ ps -ef | gr
On Friday 29 August 2008, Hal Vaughan wrote:
> On Friday 29 August 2008, Mumia W.. wrote:
> > On 08/29/2008 11:29 AM, Hal Vaughan wrote:
> > > I recently had a system drive crash on a Sarge system, so when I
> > > put in a new drive, I installed Etch (also figuring that will
> > > make upgrading to
On Friday 29 August 2008, Mumia W.. wrote:
> On 08/29/2008 11:29 AM, Hal Vaughan wrote:
> > I recently had a system drive crash on a Sarge system, so when I
> > put in a new drive, I installed Etch (also figuring that will make
> > upgrading to Lenny easier). Everything seems to have gone well,
>
On 08/29/2008 11:29 AM, Hal Vaughan wrote:
I recently had a system drive crash on a Sarge system, so when I put in
a new drive, I installed Etch (also figuring that will make upgrading
to Lenny easier). Everything seems to have gone well, except for one
point: Cron is not behaving well.
[...]
I recently had a system drive crash on a Sarge system, so when I put in
a new drive, I installed Etch (also figuring that will make upgrading
to Lenny easier). Everything seems to have gone well, except for one
point: Cron is not behaving well.
After installing my packages and getting everythi
louie miranda said:
> I have a script that is on a cron basis, It runs every hour.
> I have read a document that if you dont want any output.
> You can add >/dev/null 1>&2 to redirect it to /dev/null
> But i still received email about those output, is this syntax
> im trying to add on my cron for d
Ah yeah, thanks!
--
thanks,
louie miranda
- Original Message -
From: "Travis Crump" <[EMAIL PROTECTED]>
To: "Debian User List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 1:01 PM
Subject: Re: redirecting output to /dev/null on cron not working
louie miranda wrote:
I have a script that is on a cron basis, It runs every hour.
I have read a document that if you dont want any output.
You can add >/dev/null 1>&2 to redirect it to /dev/null
But i still received email about those output, is this syntax
im trying to add on my cron for debian co
I have a script that is on a cron basis, It runs every hour.
I have read a document that if you dont want any output.
You can add >/dev/null 1>&2 to redirect it to /dev/null
But i still received email about those output, is this syntax
im trying to add on my cron for debian correct?
/scripts/cron_
;) A try I will Give it. (Yoda)
-Original Message-
From: Jonathan Gift [mailto:[EMAIL PROTECTED]
Sent: Friday, March 02, 2001 12:19 PM
To: Martin Marconcini
Cc: Debian
Subject: Re: Log Rotate on Debian via Cron Not working!
Martin Marconcini wrote:
> Andreas, Yes, my computer is runn
Martin Marconcini wrote:
> Andreas, Yes, my computer is running 24 hs... But in case it's now i will
> check anacron. BTW: how is it configured?
BTW, none of my cron items were running and I had it on my list of
things to look at later. I read the earlier post and loaded anacron and
BANG it starte
te on Debian via Cron Not working!
On Thu, Mar 01, 2001 at 07:30:03PM -0300, Martin Marconcini wrote:
> Hi, I have indicated syslog to log kernel msgs onto /var/log/kernel
>
> Now Since i use ipmasq with some loggin the file will is growing fast...
2mb
> per day.
>
> I'd
On Thu, Mar 01, 2001 at 07:30:03PM -0300, Martin Marconcini wrote:
> Hi, I have indicated syslog to log kernel msgs onto /var/log/kernel
>
> Now Since i use ipmasq with some loggin the file will is growing fast... 2mb
> per day.
>
> I'd like to set a cron job that keeps a couple of days back logs
Hi, I have indicated syslog to log kernel msgs onto /var/log/kernel
Now Since i use ipmasq with some loggin the file will is growing fast... 2mb
per day.
I'd like to set a cron job that keeps a couple of days back logs and starts
a new each day.
How is cron setted up on Debian? Could not make it
26 matches
Mail list logo
