No, it is not a bug. It is how cron (and *IX, in general) works. I,
again, suggest you read the man pages. cron will log, or not, depending
on the settings of the '-L' parameter. I am closing this as an OPINION.
** Changed in: cron (Ubuntu)
Status: New = Opinion
--
You received this bug
So you are saying that the program ran, but it ran outside my view?
Shouldn't cron give the user feedback about when this happens?
** Changed in: cron (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
No, I did not say that. I said -- and repeat -- that -L4 will log
*failures*. No failure logged. Please do read the cron man pages.
Closing INVALID -- not a bug.
** Changed in: cron (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
I am not talking about the L4 thing. It should tell the user when their
command runs outside of x, using a popup window or that message thing in
the system tray, by default, without any special log command. windows
gives feedback if there is a problem with a schedule. OSX does too. So
cron not
I followed the instructions and restarted cron, then set up a one time
event with the command that never works, /usr/bin/redshift, but nothing
shows up in /var/log still, or on my terminal.
** Changed in: cron (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
Well.
With '-L4', cron will log all failed jobs. So, if you do not see any
output, that means it did not fail. For other possible values for '-L',
see 'man cron'.
Please note that did not fail is NOT the same as it did what I
wanted.
Now, I hope you realise that redshift will not really work if
cron is started automatically on boot. If you try to start it manually,
it will fail as you show.
Either change /etc/init/cron.conf to add your parameters, or create
/etc/init/cron.override with *just* the following line:
exec cron -L4
And then 'sudo restart cron'.
--
You received this bug
The error is $ sudo cron -L 4
cron: can't lock /var/run/crond.pid, otherpid may be 11821: Resource
temporarily unavailable
even if I kill that it only changes the number.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I would know there are errors because cron commands that I had set up
stopped working after upgrading to 13.04.
** Changed in: cron (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you. Still, it seems you have not read all I wrote, so I will
repeat:
cron, by default, will not log any errors (default loglevel is 1 --
only log cron jobs startup).
So, if you want cron to log more, you have to change the default
setting. Please see 'man cron' for the possible values.
cron, by default, will not log any errors (default loglevel is 1 -- only
log cron jobs startup). How do you know there are errors?
** Changed in: cron (Ubuntu)
Importance: Undecided = Low
** Changed in: cron (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
Are you looking for logs from the cron daemon itself, or from the
programs that cron is running? Cron sends errors by email to whoever is
specified in the MAILTO environment variable, or to the root user.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
--
You received
From cron itself
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002061
Title:
cron does not log information
To manage notifications about this bug go to:
** Package changed: ubuntu = cron (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002061
Title:
cron does not log information
To manage notifications about this bug go to:
14 matches
Mail list logo
