Your message dated Wed, 13 Jul 2016 22:00:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#786443: inhibit while a PID is running
has caused the Debian Bug report #786443,
regarding inhibit while a PID is running
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.)
--
786443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786443
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-17
Severity: wishlist
File: /bin/systemd-inhibit
Instead of inhibiting while a command spawned is running, please
find a way to elegantly/efficiently inhibit while another process is
running (e.g. a system backup).
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.26.2-2
ii libc6 2.19-18
ii libcap2 1:2.24-8
ii libcap2-bin 1:2.24-8
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.3-2
ii libkmod2 20-1
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-17
ii mount 2.26.2-2
ii sysv-rc 2.88dsf-59
ii udev 215-17
ii util-linux 2.26.2-2
Versions of packages systemd recommends:
ii dbus 1.9.16-2
ii libpam-systemd 215-17
Versions of packages systemd suggests:
pn systemd-ui <none>
-- debconf-show failed
--
.''`. martin f. krafft <[email protected]> @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
--- Begin Message ---
also sprach Michael Biebl <[email protected]> [2016-01-30 23:54 +0100]:
> >> Can you be more specific how you envision this to work? Afaics
> >> this is inherently racy, so I'm not sure if it's a good idea to
> >> provide such an interface.
> >
> > Is it racy?
>
> Sure. Between starting the program, finding out the process ID, starting
> systemd-inhibit, there is a potentially a huge window where a suspend
> request can happen.
Sure, we won't ever get rid of the race entirely, but at least in my
case, the race isn't such a problem.
Anyway, running 'systemd-inhibit whilerunning' shall do for me,
where whilerunning is left as an exercise to the reader… closing.
--
.''`. martin f. krafft <[email protected]> @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
review of a chemistry paper:
"paper should be greatly reduced or completely oxidized."
-- frank vastola
signature.asc
Description: PGP signature
--- End Message ---
