tion of SAT in column 5 trumps your
specification of column 3.
The man page contains an example for how to work around this.
--
Christian Kastner
** Changed in: cron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
This was fixed in -121.
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1110147
Title:
Error in manual
I'm afraid that this is by design, to prevent a malicious user from
dumping basically anything into one of the crontab directories.
An attacker once compromised a debian.org host by triggering a crafted
core dump in one of the crontab directories, and the daemon kept trying
to execute lines until
Hi,
On 2015-03-07 18:16, sgofferj wrote:
> On my main server I see unexplainable time jumps backwards in the syslog.
> Those jumps affect CRON.
> Example:
>
> Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
> /storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
> Feb 10 06:49:01 nostro
This is a valid request. I've linked this bug to the corresponding bug
in Debian's cron.
** Changed in: cron (Ubuntu)
Status: Invalid => Confirmed
** Bug watch added: Debian Bug tracker #561295
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561295
** Also affects: cron (Debian) via
On 2016-01-15 00:47, Humphrey van Polanen Petel wrote:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>
> Gnome _schedule command preview=/usr/local/bin/bup
^^
That's not a cron command, that is some independent Gnome frontend. cron
only r
On 2016-01-19 04:01, Humphrey van Polanen Petel wrote:
> Just so you know, it *is* a cron command.
> Gnome Schedule is nothing but a pretty gui to crontab.
And that pretty GUI is from an entirely separate package than package
cron, against which you reported the bug.
> I suggest you be a bit more
cron jobs are started by the cron daemon which is completely unrelated
to your GUI session, or any other session that might be active for the
user.
As ccooke pointed out, if you want access to an unrelated session,
you're going to have to do it manually.
** Changed in: cron (Ubuntu)
Status
Fix
** Changed in: cron (Ubuntu)
Status: New => Fix Released
** Package changed: cron (Ubuntu) => speech-dispatcher (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/b
3.0pl1-124.1ubuntu1 contains a fix for this.
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1067779
Titl
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/794141
Title:
cron needs to re-lookup users when trying t
*** This bug is a duplicate of bug 826702 ***
https://bugs.launchpad.net/bugs/826702
** This bug has been marked a duplicate of bug 826702
crontab cuts off file names at 100 characters
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 826702 ***
https://bugs.launchpad.net/bugs/826702
** This bug has been marked a duplicate of bug 826702
crontab cuts off file names at 100 characters
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
A fix has been prepared that recognizes too long commands and produces
an error message when attempting to create one, both via crontab(1) and
cron(8). Furthermore, this limit has been documented in the man pages.
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Committed
--
You rece
In the mean time, this limit has been raised to 1000 chars.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/826702
Title:
crontab cuts off file names at 100 characters
Status
Closed as per submitter's request
** Changed in: cron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/985924
Title:
Permission denied f
While an interesting concept, I believe cron is the wrong tool for this
job. Fixing this in cron would not ensure mutual exclusion in the cases
where these scripts are called by other means, eg manual calls.
The correct solution for backup_to_media and backup_to_file -- or any
other program that n
The man page for crontab(5) states that PATH is initialized with
/usr/bin:/bin, so the tar invocation in the example is correct. Or did I
misunderstand your question?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubu
The feature you are describing is the exact purpose of anacron. Could
you elaborate what you mean by "hasn't the precision of cron"? What can
cron do that you can't do with /etc/anacrontab?
BTW, it doesn't make sense for anacron to be a full-time daemon, because
when the system is up, you already
Apparently the MTA dependency in Ubuntu's cron has been demoted from
Recommends (as it is in Debian), to a Suggests, so this bug should be
re-assigned to Ubuntu's installation documentation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Could you check your MTA's log files (and /var/log/cron.*, if you have
it) for clues as to what could be going on? I just tried this locally
and it works fine: both mails are sent, and the MAILTO header is
included.
--
You received this bug notification because you are a member of Ubuntu
Touch se
This is mandated by POSIX, see
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html
** Changed in: cron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
OK, closing then. Thank you for your quick reply!
** Changed in: cron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1148594
Title:
[
Perhaps I should have been more clearer: the POSIX standard mandates
that the command field (that's everything in the sixth column of a
crontab file) be passed as arguments to /bin/sh:
| The sixth field of a line in a crontab entry is a string
| that shall be executed by sh at the specified ti
Re-assigning to dash then.
** Package changed: cron (Ubuntu) => dash (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1337576
Title:
dash inability - cron starts bina
25 matches
Mail list logo
