Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1265136

Bug#1115317: Technical Committee resolution on /var/lock and systemd

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Helmut Grohne <helmut@subdivi.de> writes:

>> Is there a reason the /var/lock directory MUST be provided by systemd
>> and no other package could provide it?
>
> systemd used to install /usr/lib/tmpfiles.d/debian.conf with a line
>
>     d /run/lock    1777 root root -   -
>
> overriding the systemd upstream configuration
> /usr/lib/tmpfiles.d/legacy.conf containing
>
>     d /run/lock 0755 root root -
>
> as the earlier lexicographical occurrence takes precedence. We could
> have a file /usr/lib/tmpfiles.d/fhs_run_lock.conf adding this back and
> it could also be installed by a different package, so yeah what you're
> proposing could be a middle ground.

Thanks for explaining!  Okay if this is just a one-line snippet, it
seems like a lot of work, but good to know it is feasible.

> Also keep in mind that we cannot just move packages from /var/lock based
> locking to flock() based locking one at a time. If two different
> packages compete about a device and they use different locking schemes,
> they'll both think they had exclusive access. Going for flock()
> practically needs to be a flag-day transition where all packages are
> updated at roughly the same time.

That seems like an archeological excursion, and I'm not sure it is the
best use of everyone's time...  maybe some other catch-all approach
could be designed to detect when two applications are using the same
device and deal with the lock problem.

Or merely give up and document that for a (possibly indefinite)
transition period, locking will be broken and users needs to take care
of this problem themselves.  This would allow partial and incremental
migrations towards flock() until all application are updated.

/Simon

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981) Thorsten Alteholz <debian@alteholz.de> - 2025-09-15 16:50 +0200
  Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981) Bdale Garbee <bdale@gag.com> - 2025-09-15 19:10 +0200
  Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981) Matthew Vernon <matthew@debian.org> - 2025-09-24 11:10 +0200
    Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981) Marco d'Itri <md@Linux.IT> - 2025-09-25 19:30 +0200
      Bug#1115317: Draft Ballot Re: Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981) Matthew Vernon <matthew@debian.org> - 2025-09-29 19:10 +0200
        Bug#1115317: Draft Ballot Re: Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981) Matthew Vernon <matthew@debian.org> - 2025-09-30 00:10 +0200
  Bug#1115317: call for votes Matthew Vernon <matthew@debian.org> - 2025-10-02 15:30 +0200
    Bug#1115317: call for votes Matthew Vernon <matthew@debian.org> - 2025-10-02 15:40 +0200
      Bug#1115317: call for votes Paul Tagliamonte <paultag@debian.org> - 2025-10-03 15:30 +0200
    Bug#1115317: call for votes Stefano Rivera <stefanor@debian.org> - 2025-10-04 18:00 +0200
    Bug#1115317: call for votes Timo Röhling <roehling@debian.org> - 2025-10-05 13:20 +0200
    Bug#1115317: call for votes Matthew Garrett <mjg59@srcf.ucam.org> - 2025-10-06 19:10 +0200
    Bug#1115317: call for votes Helmut Grohne <helmut@subdivi.de> - 2025-10-06 23:50 +0200
    Bug#1115317: call for votes Christoph Berg <myon@debian.org> - 2025-10-07 14:50 +0200
  Bug#1115317: call for votes Craig <csmall@debian.org> - 2025-10-06 23:00 +0200
    Bug#1115317: call for votes Matthew Vernon <matthew@debian.org> - 2025-10-06 23:30 +0200
  Bug#1115317: Technical Committee resolution on /var/lock and systemd Matthew Vernon <matthew@debian.org> - 2025-10-07 11:10 +0200
    Bug#1110980: Bug#1115317: Technical Committee resolution on /var/lock and systemd Simon Josefsson <simon@josefsson.org> - 2025-10-07 14:00 +0200
      Bug#1110980: Bug#1115317: Technical Committee resolution on /var/lock and systemd Santiago Vila <sanvila@debian.org> - 2025-10-07 14:30 +0200
      Bug#1110980: Bug#1115317: Technical Committee resolution on /var/lock and systemd Helmut Grohne <helmut@subdivi.de> - 2025-10-07 19:30 +0200
        Bug#1115317: Technical Committee resolution on /var/lock and systemd Simon Josefsson <simon@josefsson.org> - 2025-10-07 19:30 +0200
      Bug#1110980: Bug#1115317: Technical Committee resolution on /var/lock and systemd Marco d'Itri <md@Linux.IT> - 2025-10-07 22:10 +0200

csiph-web