On Mon, Dec 09, 2024 at 17:08:31 +, Darac Marjal wrote:
> A helpful tool here might be "cronic" (in the "cronic" package). "cronic"
> will swallow the output of the command it runs UNLESS that command exits
> with an error code.
>
> So one would write:
>
> 3 8 * * * cronic /usr/local/bin/hear
On 09/12/2024 15:30, Greg Wooledge wrote:
On Mon, Dec 09, 2024 at 15:59:38 +0100, to...@tuxteam.de wrote:
On Mon, Dec 09, 2024 at 03:24:06PM +0100, Roger Price wrote:
I added lines to /etc/crontab such as
# Watch over the NUT heartbeat at 0803 hr every day
38* * * nut/usr/loc
On 09/12/2024 15:30, Greg Wooledge wrote:
On Mon, Dec 09, 2024 at 15:59:38 +0100, to...@tuxteam.de wrote:
On Mon, Dec 09, 2024 at 03:24:06PM +0100, Roger Price wrote:
I added lines to /etc/crontab such as
# Watch over the NUT heartbeat at 0803 hr every day
38* * * nut/usr/loc
On Mon, 9 Dec 2024, Greg Wooledge wrote:
.. let it email the output to you (or whoever "nut" is).
nut is the user created by the NUT (Network UPS Tools) package which manages my
UPS units. Anyone who installs nut to manage UPS's will have this user.
Roger
On Mon, 9 Dec 2024 10:31:38 -0500
Greg Wooledge wrote:
> > In which event cron will send a complaining email to the appropriate
> > user. Since Mr. Price hasn't mentioned any such emails, I
> > conjecture he is not monitoring his emails in /var/mail, and
> > probably should be.
>
> The redirec
On Mon, 9 Dec 2024, Greg Wooledge wrote:
On Mon, Dec 09, 2024 at 15:59:38 +0100, to...@tuxteam.de wrote:
I added a username, but crontab -e didn't complain.
I still fear your crontab won't do what you expect it to do.
Most probably cron will just see what you intended as a user
name as part
On Sun, 8 Dec 2024, Greg Wooledge wrote:
What line did you add to /etc/crontab? Please paste it here. Note
that /etc/crontab uses a different format than personal crontab
files (there's an extra username field).
I added lines to /etc/crontab such as
# Watch over the NUT heartbeat at 0803 h
On Mon, Dec 09, 2024 at 08:30:16 -0700, Charles Curley wrote:
> On Mon, 9 Dec 2024 15:59:38 +0100
> wrote:
>
> > Most probably cron will just see what you intended as a user
> > name as part of the command:
> >
> > rprice /mnt/home/rprice/bark/bark.sh 11 > /dev/null 2>&1
> >
> > will run the
On Mon, Dec 09, 2024 at 15:59:38 +0100, to...@tuxteam.de wrote:
> On Mon, Dec 09, 2024 at 03:24:06PM +0100, Roger Price wrote:
> > I added lines to /etc/crontab such as
> >
> > # Watch over the NUT heartbeat at 0803 hr every day
> > 38* * * nut/usr/local/bin/heartbeat-watcher.sh > /
On Mon, 9 Dec 2024 15:59:38 +0100
wrote:
> Most probably cron will just see what you intended as a user
> name as part of the command:
>
> rprice /mnt/home/rprice/bark/bark.sh 11 > /dev/null 2>&1
>
> will run the command "rprice" on the args "/mnt..."; most of
> the time this will be a "no s
On Mon, Dec 09, 2024 at 03:24:06PM +0100, Roger Price wrote:
> On Sun, 8 Dec 2024, Greg Wooledge wrote:
>
> > What line did you add to /etc/crontab? Please paste it here. Note
> > that /etc/crontab uses a different format than personal crontab
> > files (there's an extra username field).
>
> I
On Sun, Dec 08, 2024 at 11:19:52 +0100, Roger Price wrote:
> With emacs I made a change to /etc/crontab on a Debian 11 workstation. I
> have done this before successfully. After the change I ran
>
> systemctl restart cron && systemctl status cron
>
> But now the change doesn't take effect.
>
On Sun, 8 Dec 2024, debian-u...@howorth.org.uk wrote:
Roger Price wrote:
With emacs I made a change to /etc/crontab on a Debian 11
When you say you made a change with emacs, what command did you run?
emacs /etc/crontab
What you are supposed to do is use the command crontab to start the
Roger Price wrote:
> With emacs I made a change to /etc/crontab on a Debian 11
> workstation. I have done this before successfully.
When you say you made a change with emacs, what command did you run?
What you are supposed to do is use the command crontab to start the
editor of your choice. You
On 8 Dec 2024 11:19 +0100, from deb...@rogerprice.org (Roger Price):
> What is the correct way to get cron to read the new crontab ?
Saving the crontab file.
It should be re-read automatically, with no need to restart a
system-level service.
Either you also did something else which you do not me
15 matches
Mail list logo
