Your message dated Mon, 26 Apr 2010 20:01:30 +0200
with message-id <[email protected]>
and subject line Re: Bug#348663: this bug/#348663 - Fresh install does not
start cron.d configs
has caused the Debian Bug report #348663,
regarding Fresh install does not start cron.d configs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
348663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348663
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-86
Severity: minor
Hi,
I have a fresh instalation of Sarge from CD. I put my config into
/etc/cron.d/ but the command is not started in the configured time.
'/etc/init.d/cron reload' does not help, I have to do '/etc/init.d/cron
restart', then the cron works as exptected.
Maybe the problem is in the time zone change. Preseeds of base-config are
set to:
base-config tzconfig/gmt boolean false
base-config tzconfig/preseed_zone string Europe/Prague
Cheers
Ondra Medek
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Versions of packages cron depends on:
ii adduser 3.63 Add and remove users and groups
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libpam0g 0.76-22 Pluggable Authentication Modules l
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
Ondra Medek wrote:
> Hi,
> I am not working with that system any more and I am now on a long
> travel around SE Asia, sorry.
>
> On 3/9/08, Justin Pryzby <[email protected]> wrote:
>> #348663 - Fresh install does not start cron.d configs
>> http://bugs.debian.org./348663
>>
>> Sorry that nobody responded to your report earlier. Does that system
>> still exist? Do logfiles still exist from the install (ha!). Can you
>> reproduce the problem with current install? I suspect the problem is
>> actually related to bug#433609, which involves cron not running
>> commands after it found that a symbolic link was broken (or file
>> ownership wasn't as expected, or ...).
I agree that this is almost surely another instance of #433609. Since
the OP does not appear to use that system anymore and the time passed
since sarge, I think it would be nearly impossible to trace the original
issue.
If this issue reappears on a newer Debian system, please open a new bug.
Thanks,
Christian
signature.asc
Description: OpenPGP digital signature
--- End Message ---
