merge 670118 620392
thanks
On Fri, Apr 01, 2011 at 12:26:01PM -0500, Adam Heath wrote:
I suggest that in this case the output should be sent to syslog, at
the least.
I'm merging this bug with bug #670118 which provides precisely support
for logging cron job information to syslog.
This
On Fri, Apr 01, 2011 at 08:37:23PM +0200, Christian Kastner wrote:
Logging to syslog could be an idea worth entertaining, but it would have
to be implemented via a configurable option.
Logging of output of cron jobs to syslog is not something I would think of
being a good idea. There's a lot of
On 04/03/2011 04:09 PM, Javier Fernández-Sanguino Peña wrote:
On Fri, Apr 01, 2011 at 08:37:23PM +0200, Christian Kastner wrote:
Logging to syslog could be an idea worth entertaining, but it would have
to be implemented via a configurable option.
Logging of output of cron jobs to syslog is
package: cron
version: 3.0pl1-106
cron has no depends on any mta; instead, it just has a recommends.
However, when no mta is installed, the output of the job being run
gets thrown away. This is very bad, and makes debugging things difficult.
I suggest that in this case the output should be
severity 620392 wishlist
thanks
Hi Adam,
On 04/01/2011 07:26 PM, Adam Heath wrote:
package: cron
version: 3.0pl1-106
cron has no depends on any mta; instead, it just has a recommends.
However, when no mta is installed, the output of the job being run gets
thrown away. This is very bad,
5 matches
Mail list logo
