Package: acct
Version: 6.6.4-4
Severity: normal
X-Debbugs-Cc: debian-b...@henk.geekmail.org

Dear Maintainer,

   * What led up to the situation?

A mail from Anacron containing:
/etc/cron.daily/acct:
touch: cannot touch '/var/lock/subsys/acct': No such file or directory

Running the initscript manually gives the same error.

(Accounting needs to be enabled in /etc/default/acct or the error will
not occur)

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

/var/lock/subsys/ does not exist on my sysvinit-based systems:
# namei -l '/var/lock/subsys/acct'
f: /var/lock/subsys/acct
drwxr-xr-x root root /
drwxr-xr-x root root var
lrwxrwxrwx root root lock -> /run/lock
drwxr-xr-x root root   /
drwxr-xr-x root root   run
drwxrwxrwt root root   lock
                     subsys - No such file or directory

AFAIU this directory is created on systemd-based systems but does not
seem to get created on sysvinit-based systems.
Since it’s on a tmpfs, creating it manually would not help permanently:
# df -h /var/lock/
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           5.0M     0  5.0M   0% /run/lock


I don’t know where this directory is supposed to be coming from on
sysvinit-based systems.
Maybe the acct initscript should check whether it exists and create it
if needed?

Thanks

Hendrik


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-15-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages acct depends on:
ii  init-system-helpers  1.60
ii  libc6                2.31-13+deb11u3
ii  lsb-base             11.1.0

acct recommends no packages.

acct suggests no packages.

-- no debconf information

Reply via email to