tags #833955 confirmed pending
thanks
On Thu, Aug 11, 2016 at 04:10:54AM +0200, Vincent Lefevre wrote:
> What is the goal of theses .../subsys commands in /etc/init.d/atop*?
I think it's what upstream uses as a "pidfile for the poor". The init
scripts should really use start-stop-daemon or
On Thu, Aug 11, 2016 at 04:10:54AM +0200, Vincent Lefevre wrote:
> On 2016-08-10 22:38:27 +0200, Marc Haber wrote:
> > On Wed, Aug 10, 2016 at 10:17:07PM +0200, Vincent Lefevre wrote:
> > > Here the /var/lock/subsys directory doesn't exist, yielding an error
> > > message, and the file is not
On 2016-08-10 22:38:27 +0200, Marc Haber wrote:
> On Wed, Aug 10, 2016 at 10:17:07PM +0200, Vincent Lefevre wrote:
> > Here the /var/lock/subsys directory doesn't exist, yielding an error
> > message, and the file is not created.
>
> Can you try changing that to /run/lock/subsys/atop{acctd}
tags #833955 confirmed
thanks
On Wed, Aug 10, 2016 at 10:17:07PM +0200, Vincent Lefevre wrote:
> /etc/init.d/atop and /etc/init.d/atopacct scripts have:
>
> touch /var/lock/subsys/atop
> rm /var/lock/subsys/atop
>
> and
>
> touch /var/lock/subsys/atopacctd
> rm
Package: atop
Version: 2.2.3-1~exp1
Severity: minor
/etc/init.d/atop and /etc/init.d/atopacct scripts have:
touch /var/lock/subsys/atop
rm /var/lock/subsys/atop
and
touch /var/lock/subsys/atopacctd
rm /var/lock/subsys/atopacctd
respectively.
Here the /var/lock/subsys directory
5 matches
Mail list logo