Your message dated Sun, 15 Nov 2009 21:19:42 +0900
with message-id <[email protected]>
and subject line Re: Bug#407900: at: no /var/run/atd.pid
has caused the Debian Bug report #407900,
regarding at: no /var/run/atd.pid
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.)
--
407900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407900
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: at
Version: 3.1.10
Severity: important
can set at jobs because:
# at 13:00
warning: commands will be executed using /bin/sh
at> apt-get update && apt-get -d dist-upgrade
at> <EOT>
job 5 at Mon Jan 22 13:00:00 2007
Can't open /var/run/atd.pid to signal atd. No atd running?
-bash-3.1# pidof atd
3565
-bash-3.1# ps ax|grep atd
3565 ? Ss 0:00 /usr/sbin/atd
4160 ? Ss 0:00 /sbin/rpc.statd
7977 pts/1 S+ 0:00 grep atd
that's it - guess the tmpfs saga for /var/run has bitten atd pkg too ...
thanks
--
paolo
--- End Message ---
--- Begin Message ---
Hi,
oopla-pzp <[email protected]> writes:
> On Sat, Nov 14, 2009 at 02:38:56PM +0900, Ansgar Burchardt wrote:
>> tags 407900 + unreproducible
>
> old bug indeed, never hit again so far
>
>> I cannot reproduce your problem here. /var/run/atd.pid is created here.
>> Are the permissions for /var/run correct?
>
> yes perms are/were ok. As said, problem is/was that initscript(s) is(are)
> too dumb, since they assume that the absence of /var/run/demon.pid means
> really no running demon for sure, without checking with ps(1).
> Well, that might be on puropose, but rather annoying and never got any
> supposed advantage.
>
> Feel free to close it if you deem so, should I have stumble on it agin I'd
> (re)open it or open a new one.
Okay, will do so.
Regards,
Ansgar
--- End Message ---
