Summary: | net-analyzer/iptraf-ng-1.1.3.1-r1 - Cannot write to '/var/lock' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jorge Manuel B. S. Vicetto (RETIRED) <jmbsvicetto> |
Component: | Current packages | Assignee: | Gentoo Netmon project <netmon> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | flameeyes, mail, releng |
Priority: | Normal | ||
Version: | autobuilds | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 332633 |
Description
Jorge Manuel B. S. Vicetto (RETIRED)
![]() Same thing here. Only seems to happen on fresh installs: /var/lock is linked to /run/lock so I fixed it by mkdir /run/lock *** Bug 449536 has been marked as a duplicate of this bug. *** I don't readily see how this bug or its duplicate is related to bug #332633 unless we revise that tracker bug's purpose. We should rather set up a new tracker bug for /var/lock. /var/lock has been changed the same way as /var/run with the introduction of /run. We can rename it to "keepdir-var-run-lock" but I don't think it's worth it. It's basically the same problem, /var/lock should not be packaged, but rather created by init scripts. iptraf-ng, like many other packages, uses $localstatedir to determine what to use for PREFIX/[[[var/]]]{lib,log,lock}/iptraf-ng. Now some of these move to /run/ (lock) while some others do not (lib, log).</rant> (In reply to comment #4) > It's basically the same problem, /var/lock should not be packaged, but > rather created by init scripts. It isn't the same problem when the lock file is used when no init.d script is used. It is fine because /var/lock -> /run/lock symlink should be created by openrc itself, and should be accessible without having to change the localstatedir setting for iptraf-ng. As for the directory to be needed without an init script, that's the same as munin (on the master side), and can either be solved with a local.d file or with a recent openrc and tmpfiles.d That's odd. iptraf-ng's -B mode is broken, which helps explain why its locking features are completely unused - the only references to LOCKDIR (which points to /var/run by default) are apparently obsolete. Fixed, then. Oh, oversaw a few uses there. *overlooked It's even easier than I previously assumed. The subdir is created automatically when missing so there is no need for keepdir, we just need to make sure /run/lock is used instead of /var/lock. Fixed in the stable ebuild too, since this is a build error, after all. |