On Sun 17 May 2020 at 19:14:46 (-0600), ghe wrote:
> On Sunday, May 17, 2020 4:48 PM, David Wright
> wrote:
>
> > OK, I thought you might list both. I'm not actually sure where output
> > goes because I always have MAILTO set, which takes care of it.
>
> Since I don't know what MAILTO is, I sus
On Sun, May 17, 2020 at 11:21:11AM -0600, ghe wrote:
> > Cron jobs (some of them) don't show up in root's email.
Which MTA are you using, and how did you configure its behavior for
mail addressed to "root"?
Some MTAs will deliver literally to root's inbox (/var/mail/root or
some other place). Ot
On Du, 17 mai 20, 19:14:46, ghe wrote:
>
> Is MAILTO an environmental var? There's no MAILTO in 'env' when root or
> backup (the amanda user) or ghe (me). There's a MAIL in the users'
> environments, but I don't think that's what you're talking about. It's
> pointed at /var/mail/ anyway.
See man
‐‐‐ Original Message ‐‐‐
On Sunday, May 17, 2020 4:48 PM, David Wright
wrote:
> OK, I thought you might list both. I'm not actually sure where output
> goes because I always have MAILTO set, which takes care of it.
Since I don't know what MAILTO is, I suspect I've never had to have it
On Sun 17 May 2020 at 13:05:39 (-0600), ghe wrote:
> On Sunday, May 17, 2020 12:03 PM, David Wright
> wrote:
>
> > I always examine my cron with
> >
> > crontab -l
> >
> > rather than just catting some random file.
>
> Here it is, but I see no difference, except the disabled tripwire.
>
> root
‐‐‐ Original Message ‐‐‐
On Sunday, May 17, 2020 12:03 PM, David Wright
wrote:
> I always examine my cron with
>
> crontab -l
>
> rather than just catting some random file.
>
> Cheers,
> David.
Here it is, but I see no difference, except the disabled tripwire.
root@sbox:~# crontab
On Sun 17 May 2020 at 11:21:11 (-0600), ghe wrote:
> On 5/17/20 10:42 AM, ghe wrote:
> > Buster, Supermicro desktop
> >
> > Cron jobs (some of them) don't show up in root's email.
> >
> > I admin 2 domains -- one on Squeeze, one on Buster. My Squeeze
> > cron results show up fine; Buster's don't.
On 5/17/20 10:42 AM, ghe wrote:
Buster, Supermicro desktop
Cron jobs (some of them) don't show up in root's email.
I admin 2 domains -- one on Squeeze, one on Buster. My Squeeze cron
results show up fine; Buster's don't. I've reinstalled the Buster jobs.
I've copyNpasted them from the Squeeze
On Sun, Feb 22, 2004 at 10:57:27PM +0530, Deboo wrote:
[...]
> When played manually, it
> plays fine (I use the "play" utility toplay it from cron), but from cron,
> the sound output is very distorted.
[...]
Interesting.
Some probably-not-very-useful idea
I use a small wav file which sounds like an old wallclock dong for
sounding the number of hours, using cron. When played manually, it
plays fine (I use the "play" utility toplay it from cron), but from cron,
the sound output is very distorted. Even if nothing else is running on the
system, it's dis
On Fri, 2002-12-13 at 10:43, Oliver Elphick wrote:
> So run "/bin/run-parts --verbose /etc/cron.daily" and see where the
> error is occurring. Then take the offending scripts from
> /etc/cron.daily/* and turn on debugging (for example add set -x near the
> top of the script) so that you can see
On Fri, 2002-12-13 at 11:58, Ludwig wrote:
> This only started a week or two ago: I've been getting emails from the
> cron daemon indicating a problem with /etc/crontab or cron itself. I've
> tried using crontab to regenerate /etc/crontab, and purging and
> reinstalling cron, and but am still get
This only started a week or two ago: I've been getting emails from the
cron daemon indicating a problem with /etc/crontab or cron itself. I've
tried using crontab to regenerate /etc/crontab, and purging and
reinstalling cron, and but am still getting the following:
From: Cron Daemon <[EMAIL PROT
On Thu, Feb 14, 2002 at 02:06:37PM -0200, Michel Loos wrote:
> your /etc/cron.daily/exim file is not adapted to your way of logging
> exim.
>
> You possibly answered N, while upgrading exim, for the replacement of
> this file. I fthis is the case you should have a
> /etc/cron.daily/exim.dpkg* fil
On Thu, 2002-02-14 at 13:30, David Frey wrote:
> I am getting this message from cron everyday:
>
> /etc/cron.daily/exim:
> chown: getting attributes of `/var/log/exim/mainlog.new': No such file
> or directory
> chmod: getting attributes of `/var/log/exim/mainlog.new': No such file
> or directory
>
I am getting this message from cron everyday:
/etc/cron.daily/exim:
chown: getting attributes of `/var/log/exim/mainlog.new': No such file
or directory
chmod: getting attributes of `/var/log/exim/mainlog.new': No such file
or directory
mv: cannot stat `/var/log/exim/mainlog.new': No such file or d
Hi all,
Out of the blue about ten days ago I started getting an odd error from
cron every morning. Looks like some kind of shell escaping error with
find (i've attached today's) in /etc/cron.daily/standard. However,
all of the find lines in that script are commented out. I imagine
there's some
That's okay. It's at least nice to know I'm not the only one. :)
Bill.
On Wed, 26 Aug 1998, M.C. Vernon wrote:
>
> >
> > Hi there. Cron doesn't seem to be running on our Debian machine. There
> > is one job in the root crontab and I started it with a #crontab root
> > command. #crontab -l
>
> Hi there. Cron doesn't seem to be running on our Debian machine. There
> is one job in the root crontab and I started it with a #crontab root
> command. #crontab -l shows the job but it never runs. Any ideas or
> experience with this? If you need more info just let me know. Thanks in
>
Hi there. Cron doesn't seem to be running on our Debian machine. There
is one job in the root crontab and I started it with a #crontab root
command. #crontab -l shows the job but it never runs. Any ideas or
experience with this? If you need more info just let me know. Thanks in
advance.
Reg
Lawrence Chim wrote:
>
> I don't know why cron always send mail to root with the following
> body. Any idea?
>
I think what you are asking to related to the "MAILTO" variable.
If you set MAILTO='' in your crontab for root the cron stuff
will not be sent.
An exerpt from the cron man page:
Lawrence Chim <[EMAIL PROTECTED]> writes:
>
> [1 ]
> Rick Macdonald wrote:
> >
> > Lawrence Chim wrote:
> > >
> > > I don't know why cron always send mail to root with the following
> > > body. Any idea?
> > >
> > > Subject: Cron <[EMAIL PROTECTED]> run-parts /etc/cron.daily
> > > X-Cron-Env:
Rick Macdonald wrote:
>
> On Thu, 21 Nov 1996, Lawrence Chim wrote:
>
> > Rick Macdonald wrote:
> > >
> > > Lawrence Chim wrote:
> > > >
> > > > I don't know why cron always send mail to root with the following
> > > > body. Any idea?
> > > >
> > > > Subject: Cron <[EMAIL PROTECTED]> run-parts /
On Thu, 21 Nov 1996, Lawrence Chim wrote:
> Rick Macdonald wrote:
> >
> > Lawrence Chim wrote:
> > >
> > > I don't know why cron always send mail to root with the following
> > > body. Any idea?
> > >
> > > Subject: Cron <[EMAIL PROTECTED]> run-parts /etc/cron.daily
> > > getopt: illegal option
On Thu, 21 Nov 1996, Lawrence Chim wrote:
> I don't know why cron always send mail to root with the following
> body. Any idea?
>
> Subject: Cron <[EMAIL PROTECTED]> run-parts /etc/cron.daily
> X-Cron-Env:
> X-Cron-Env:
>
> X-Cron-Env:
> X-Cron-Env:
>
> getopt: illegal option -- o
>
> lawr
Rick Macdonald wrote:
>
> Lawrence Chim wrote:
> >
> > I don't know why cron always send mail to root with the following
> > body. Any idea?
> >
> > Subject: Cron <[EMAIL PROTECTED]> run-parts /etc/cron.daily
> > X-Cron-Env:
> > X-Cron-Env:
> >
> > X-Cron-Env:
> > X-Cron-Env:
> >
> > getopt:
I don't know why cron always send mail to root with the following
body. Any idea?
Subject: Cron <[EMAIL PROTECTED]> run-parts /etc/cron.daily
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
getopt: illegal option -- o
lawrence,
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "uns
27 matches
Mail list logo
