Re: cron problem

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

Re: cron problem

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).

Re: cron problem

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

Re: cron problem

‐‐‐ 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

Re: cron problem

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. > >

Re: cron problem

‐‐‐ 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:~#

Re: cron problem

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

Re: cron problem

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

cron Problem

Hallo Leute, ich habe mir mal zum Test ein einfaches Script (ntpdate.sh) erstellt. -- #!/bin/sh ntpdate -sbuv 192.168.45.3 -- dieses Script habe ich in das Verzeichnis cron.hourly kopiert. Es wird auch jede Stunde

Re: cron Problem

Saskia Whigham [EMAIL PROTECTED] schrieb: Hallo Leute, ich habe mir mal zum Test ein einfaches Script (ntpdate.sh) erstellt. -- #!/bin/sh ntpdate -sbuv 192.168.45.3 -- dieses Script habe ich in das

AW: cron Problem

den absoluten Pfad habe ich angegeben funzt aber trotzdem nicht. -Ursprüngliche Nachricht- Von: Andreas Kretschmer,,, [mailto:[EMAIL PROTECTED] Auftrag von Andreas Kretschmer Gesendet: Donnerstag, 7. April 2005 16:29 An: debian-user-german@lists.debian.org Betreff: Re: cron Problem

Re: cron Problem

Am 2005-04-07 16:04:03, schrieb Saskia Whigham: Hallo Leute, dieses Script habe ich in das Verzeichnis cron.hourly kopiert. Es wird auch ^^^ herein zu kopieren. Meine /etc/crontab habe ich nicht verändert will sagen

Re: cron Problem

am 07.04.2005, um 16:58:24 +0200 mailte Thomas folgendes: den absoluten Pfad habe ich angegeben funzt aber trotzdem nicht. 1. warum einklich eine extra Mailkopie an privat? 2. bist Du Saskia oder Thomas? 3. könntest Du http://learn.to/quote bitte sinnentnehmend lesen? Danke. 4. 'funzt' kenn ich

Re: cron Problem

On Thu, Apr 07, 2005 at 05:18:41PM +0200, Michelle Konzack wrote: Es gibt kein Verzeichnis cron.hourly also hast Du es angelegt. Nicht auf Woody, aber es existiert auf Sarge. -- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum

Re: cron Problem

Woher weisst du das es nicht ausgefuehrt wird? Meine Vermutung ist eine /etc/adjtime mit fehlerhaftem Inhalt. -- Peter -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject

Re: cron Problem

am 07.04.2005, um 17:38:24 +0200 mailte Peter Wiersig folgendes: Woher weisst du das es nicht ausgefuehrt wird? Meine Vermutung ist eine /etc/adjtime mit fehlerhaftem Inhalt. Warum klappt es dann, wenn man es von Konsole ausführt? Andreas -- Andreas Kretschmer(Kontakt: siehe Header)

Re: cron Problem

Hallo, was soll da fehlerhaft sein. Wahrscheinlich muss ich in der crontab von Sarge nch die Zeile mit cron.hourly so eintragen wie Michelle es gesagt hat. Die Zeile 0 * * * * roottest -e /usr/sbin/anacron || run-parts --report /etc/cron.hourly ist in der crontab von Sarge nicht in

Re: cron Problem

Am 2005-04-07 17:43:13, schrieb Saskia Whigham: Hallo, was soll da fehlerhaft sein. Wahrscheinlich muss ich in der crontab von Sarge nch die Zeile mit cron.hourly so eintragen wie Michelle es gesagt hat. Die Zeile 0 * * * * roottest -e /usr/sbin/anacron || run-parts --report

Re: cron Problem

Hallo, das Frage ich mich auch. Auf Konsole brauche ich nur ntpdate -sbuv 192.168.43.3 eingeben und er holt sich Ordnungsgemäß die Zeit. Pake ich das den in eine Datei und kopiere diese in cron.hourly führt er zwar cron.hourly zur angegeben Zeit die in der crontab angegeben ist aus aber die Zeit

Re: cron Problem

On Thu, Apr 07, 2005 at 04:04:03PM +0200, Saskia Whigham wrote: ich habe mir mal zum Test ein einfaches Script (ntpdate.sh) erstellt. Zeig mal die Ausgabe von run-parts --test /etc/cron.hourly. Wenn dein Skript da nicht auftaucht, koennte das am .sh liegen, auf das du auch verzichten kannst.

Re: cron Problem

Saskia Whigham [EMAIL PROTECTED] schrieb: Hallo, das Frage ich mich auch. Auf Konsole brauche ich nur ntpdate -sbuv Was, wen, auf was und wessen Aussagen beziehst Du Dich? Mit Deinem Nullquoting, gepart mit kaputten References, machst Du das einem echt schwer, Dir und Deinen Gedanken zu

Re: cron Problem

On 07.Apr 2005 - 17:43:13, Saskia Whigham wrote: Hallo, was soll da fehlerhaft sein. Wahrscheinlich muss ich in der crontab von Sarge nch die Zeile mit cron.hourly so eintragen wie Michelle es gesagt hat. Nein, die Standard-Zeile reicht vollkommen. Michelle hat mal wieder keine Ahnung (was

Re: cron Problem

Moinmoin! On Thu, Apr 07, 2005 at 06:15:48PM +0200, Peter Wiersig wrote: On Thu, Apr 07, 2005 at 04:04:03PM +0200, Saskia Whigham wrote: ich habe mir mal zum Test ein einfaches Script (ntpdate.sh) erstellt. Zeig mal die Ausgabe von run-parts --test /etc/cron.hourly. Wenn dein Skript da

Re: cron Problem

Saskia Whigham [EMAIL PROTECTED] writes: das Frage ich mich auch. Was eigentlich? Geh jetzt bitte Dir ein funktionierendes Mail-Programm holen, lerne so zu zitieren, wie es hier üblich ist und *dann*, aber erst dann komme wieder und schildere genau, was Du gemacht hast, was Du erwartest und

Re: cron Problem

Michelle Konzack [EMAIL PROTECTED] wrote: Die sollte eigentlich so aussehen: __( '/etc/crontab' )__ / | SHELL=/bin/sh | PATH=/sbin:/bin:/usr/sbin:/usr/bin | MAILTO=blubber | | # m h dom mon dow usercommand | 1 0 * * * root

Cron problem?

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

Re: Cron problem?

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 ideas of

Cron problem

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

Re: Cron problem

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

Exim Cron problem

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

Re: Exim Cron problem

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 mv:

Re: Exim Cron problem

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* file.

dumb cron problem

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

Cron problem

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.

Re: Cron problem

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

Re: Cron problem

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 shows

cron problem

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: SHELL=/bin/sh X-Cron-Env: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin X-Cron-Env: HOME=/root X-Cron-Env: LOGNAME=root

Re: cron problem

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: SHELL=/bin/sh X-Cron-Env:

Re: cron problem

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: SHELL=/bin/sh X-Cron-Env: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

Re: cron problem

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 -- o You might want

Re: cron problem

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 /etc/cron.daily getopt:

Re: cron problem

Lawrence Chim [EMAIL PROTECTED] writes: [1 text/plain; us-ascii (7bit)] 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:

Re: cron problem

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: