Re: [systemd-devel] Udev rules hardware database

Patrick Häcker [2014-11-05 16:55 +0100]: > I you want to have permanent power saving activated for your devices, the > recommended way is to use udev (e.g. > https://wiki.archlinux.org/index.php/Power_saving#USB_autosuspend). Some > [...] > - Is there already something like this? By coincidence

Re: [systemd-devel] [PATCH] smack: introduce new SmackLabelExec option

On 11/07/2014 09:35 AM, Lennart Poettering wrote: > On Fri, 07.11.14 04:17, WaLyong Cho (walyong@gmail.com) wrote: > >> SMACK64 >> Used to make access control decisions. In almost all cases >> the label given to a new filesystem object will be the label >> of the process that cr

[systemd-devel] [RFC 3/4] monitor for utab changes with inotify

Parsing the mount table with libmount races against the mount command, which will handle the actual mounting before updating utab. This means the poll event on /proc/self/mountinfo can kick of a reparse in systemd before the utab information is available. This change adds in an additional event s

[systemd-devel] [RFC 1/4] use libmount to enumerate /proc/self/mountinfo

This lets libmount add in user options from /run/mount/utab, like _netdev which is needed to get proper ordering against remote-fs.target --- .travis.yml | 2 +- Makefile.am | 4 +++- README | 1 + configure.ac | 13 src/core/build.h | 7 +++ src/core/m

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

On Fri, Oct 31, 2014 at 09:32:57AM +0100, Karel Zak wrote: > It would be really better to have within systemd a generic function > is_net_blkdev() than rely on external fragile configuration. I have > doubts that anyone uses -o _netdev on command line when manually > mounts filesystem. The one

[systemd-devel] [RFC 0/4] use libmount for mount unit handling

This patchset is an attempt to use libmount for mount unit handling, in order to address the issues I raised with the _netdev option and remote-fs ordering not working as expected. The first three patches I think are fairly complete, while the final patch may need additional work to get everything

[systemd-devel] [RFC 4/4] add remote-fs dependencies if needed after change

This is an attempt to add it the remote-fs dependencies to a mount unit if the options change, like when the utab options are picked up after mountinfo has already been processed. It just adds the remote-fs dependencies, leaving the local-fs ones in place. With this change I always get mount unit

[systemd-devel] [RFC 2/4] check options as well as fstype for network mounts

When creating a new mount unit after an event on /proc/self/mountinfo, check the mount options as well as the fstype to determine if this is a remote mount that requires network access. --- src/core/mount.c | 21 - 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/

[systemd-devel] Shutdown problems

Hello, I'm having some trouble shutting down my system with systemd. What happens is the following: * If I execute "systemctl reboot" while a text console is active, everything works fine. * If I execute "systemctl reboot" while the X11 console is active, the system hangs (I tried waitin

Re: [systemd-devel] [PATCH] unit: do not order timers.target before basic.target

On Fri, Nov 07, 2014 at 03:13:12AM +0100, Lennart Poettering wrote: > On Fri, 07.11.14 03:02, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > > I must say I kinda like the fact that pulling in and reaching > > > "basic.target" makes sure all those background things that can fire > > >

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

On Thu, Nov 6, 2014 at 6:02 PM, Lennart Poettering wrote: > On Thu, 06.11.14 17:48, Michael Marineau (michael.marin...@coreos.com) wrote: > >> > So, what's the real usecase for all of this? Can you elaborate on >> > that? >> >> The basic idea is to create a container that has the ability to return

Re: [systemd-devel] user environment variables

On Fri, 31.10.14 17:16, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > For systemd be aware of certain environment variables, I usually use a > drop-in config in /etc/systemd/system/user@service.d. This way, I can > see the varibale when running > $ systemctl --user show-environment > > Now I

Re: [systemd-devel] [PATCH] Add support for supplying an exit status code to "systemctl exit"

On Thu, 06.11.14 18:09, Vito Caputo (vito.cap...@coreos.com) wrote: > > +r = sd_bus_message_read(message, "i", &m->exit_retval); > +if (r < 0) > +return r; > + > m->exit_code = MANAGER_EXIT; > > return sd_bus_reply_method_return(message, NULL); >

Re: [systemd-devel] [PATCH] Add support for supplying an exit status code to "systemctl exit"

On Thu, 06.11.14 18:09, Vito Caputo (vito.cap...@coreos.com) wrote: > The capability of directly propagating a return code out to the caller of > systemd --user from within something like an OnFailure unit has utility. > > This also contains a minor fixup to the documentation adding "exit" to the

Re: [systemd-devel] [PATCH] unit: do not order timers.target before basic.target

On Fri, 07.11.14 03:02, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > I must say I kinda like the fact that pulling in and reaching > > "basic.target" makes sure all those background things that can fire > > have been set up for firing, and everything else can then just assume > > tha

[systemd-devel] [PATCH] Add support for supplying an exit status code to "systemctl exit"

The capability of directly propagating a return code out to the caller of systemd --user from within something like an OnFailure unit has utility. This also contains a minor fixup to the documentation adding "exit" to the --force section. Cheers, Vito Caputo --- man/systemctl.xml | 11 +

Re: [systemd-devel] [PATCH] unit: do not order timers.target before basic.target

On Fri, Nov 07, 2014 at 02:49:59AM +0100, Lennart Poettering wrote: > On Sun, 02.11.14 17:59, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > Since commit 19f8d037833f2 'timer: order OnCalendar units after > > timer-sync.target if DefaultDependencies=no' timers might get a > > depende

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

On Thu, 06.11.14 17:48, Michael Marineau (michael.marin...@coreos.com) wrote: > > So, what's the real usecase for all of this? Can you elaborate on > > that? > > The basic idea is to create a container that has the ability to return a > normal exit code when it exits. System instances don't allow

Re: [systemd-devel] [PATCH] unit: do not order timers.target before basic.target

On Sun, 02.11.14 17:59, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > Since commit 19f8d037833f2 'timer: order OnCalendar units after > timer-sync.target if DefaultDependencies=no' timers might get a > dependency on time-sync.target, which does not really belong in early > boot. If ntp

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

On Nov 6, 2014 5:17 PM, "Lennart Poettering" wrote: > > On Thu, 06.11.14 16:59, Vito Caputo (vito.cap...@coreos.com) wrote: > > > Because for all intents and purposes it's effectively still a user > > instance, just having its own PID namespace isn't cause --system behaviors > > like disabling sys

Re: [systemd-devel] [PATCH] shared/install: don't report 'static' when unit contains only Also=

On Thu, 06.11.14 10:49, Jan Synacek (jsyna...@redhat.com) wrote: > I think that this patch might be a bit ineffective, as it calls > unit_file_load() again just to get an InstallContext. I wasn't sure > how to get Also= targets in any other way. > > If such change makes sense, this patch should p

Re: [systemd-devel] [PATCH v2 2/2] bootchart: escape non printable process name

On Mon, 03.11.14 15:00, WaLyong Cho (walyong@samsung.com) wrote: > --- > src/bootchart/svg.c | 10 +++--- > 1 file changed, 7 insertions(+), 3 deletions(-) > > diff --git a/src/bootchart/svg.c b/src/bootchart/svg.c > index faf377e..e5569e1 100644 > --- a/src/bootchart/svg.c > +++ b/src/b

Re: [systemd-devel] [PATCH v2 1/2] utf8: intruduce utf8_escape_non_printable

On Mon, 03.11.14 15:00, WaLyong Cho (walyong@samsung.com) wrote: > --- > src/shared/utf8.c| 87 > > src/shared/utf8.h| 1 + > src/test/test-utf8.c | 30 ++ > 3 files changed, 118 insertions(+) > > diff --git a/src

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

On Thu, 06.11.14 16:59, Vito Caputo (vito.cap...@coreos.com) wrote: > Because for all intents and purposes it's effectively still a user > instance, just having its own PID namespace isn't cause --system behaviors > like disabling systemctl exit for example. I am pretty sure doing something like

Re: [systemd-devel] [PATCH] manager: Ensure user's systemd runtime directory exists.

On Wed, 05.11.14 14:51, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Colin Guthrie wrote on 03/11/14 08:02: > > Zbigniew Jędrzejewski-Szmek wrote on 02/11/14 18:18: > >> On Sun, Nov 02, 2014 at 02:04:20PM +, Colin Guthrie wrote: > >>> This mirrors code in dbus.c when creating the private sock

Re: [systemd-devel] Poor man's reboot doesn't work

On Sun, 02.11.14 12:48, Thomas Meyer (tho...@m3y3r.de) wrote: > Hi, > > I tried to switch to the emergency target and back to the graphical target, > but this doesn't seem to work. > > Should this work, i.e.? > > # systemctl isolate emergency.target > # systemctl isolate graphical.target > > T

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

Because for all intents and purposes it's effectively still a user instance, just having its own PID namespace isn't cause --system behaviors like disabling systemctl exit for example. Preventing exit from PID 1 makes sense when you're going to panic the kernel, but doesn't --user imply otherwise?

Re: [systemd-devel] [PATCH] smack: introduce new SmackLabelExec option

On Fri, 07.11.14 04:17, WaLyong Cho (walyong@gmail.com) wrote: > SMACK64 > Used to make access control decisions. In almost all cases > the label given to a new filesystem object will be the label > of the process that created it. > SMACK64EXEC > The Smack label of a pr

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

On Thu, 06.11.14 16:26, Vito Caputo (vito.cap...@coreos.com) wrote: > Imagine running systemd --user post-CLONE_NEWPID to manage services in the > new namespace. But why not run it as --system then? Not following... Lennart -- Lennart Poettering, Red Hat _

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

Imagine running systemd --user post-CLONE_NEWPID to manage services in the new namespace. Cheers, Vito Caputo On Thu, Nov 6, 2014 at 2:56 PM, Lennart Poettering wrote: > On Thu, 06.11.14 14:44, Vito Caputo (vito.cap...@coreos.com) wrote: > > Hmm? What is this about? Why would you want to run sy

Re: [systemd-devel] [PATCH] timer: reenable TIMER_ACTIVE timers when restarted

On Thu, 06.11.14 19:47, Michael Chapman (m...@very.puzzling.org) wrote: Makes sense! Applied! > A timer configured with OnActiveSec will start its associated unit again > if the timer is stopped, then started. However, if the timer unit is > restarted -- with "systemctl restart", say -- this does

[systemd-devel] [PATCH] timer: reenable TIMER_ACTIVE timers when restarted

A timer configured with OnActiveSec will start its associated unit again if the timer is stopped, then started. However, if the timer unit is restarted -- with "systemctl restart", say -- this does not occur. This commit ensures that TIMER_ACTIVE timers are re-enabled whenever the timer is started

Re: [systemd-devel] SELinux code in method_{disable, enable}_unit_files_generic() functions

On Tue, 04.11.14 09:17, Laurent Bigonville (bi...@debian.org) wrote: > Hello, > > After looking a bit around the code, I've two questions about the > SELinux code in method_{disable,enable}_unit_files_generic() functions. > > In method_enable_unit_files_generic(), > mac_selinux_unit_access_check

Re: [systemd-devel] Udev rules hardware database

On Thu, Nov 06, 2014 at 07:49:38PM +0100, Lennart Poettering wrote: > On Wed, 05.11.14 16:55, Patrick Häcker (pa...@web.de) wrote: > > heya, > > > sorry if this list is not the correct one for my post. In this case please > > just point me to the correct list. > > It is the correct list. > > >

Re: [systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

On Thu, 06.11.14 14:44, Vito Caputo (vito.cap...@coreos.com) wrote: Hmm? What is this about? Why would you want to run systemd --user as PID 1? > diff --git a/src/core/main.c b/src/core/main.c > index d48604e..cd9d6ee 100644 > --- a/src/core/main.c > +++ b/src/core/main.c > @@ -2013,7 +2013,7 @@

[systemd-devel] [PATCH] Allow PID 1 systemd --user instances to exit

--- src/core/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/core/main.c b/src/core/main.c index d48604e..cd9d6ee 100644 --- a/src/core/main.c +++ b/src/core/main.c @@ -2013,7 +2013,7 @@ finish: getpid() == 1 ? "freezing" : "quitting");

Re: [systemd-devel] [PATCH] s/commandline/command line/g

On Thu, 06.11.14 15:37, Lennart Poettering (lenn...@poettering.net) wrote: > On Wed, 05.11.14 14:56, har...@redhat.com (har...@redhat.com) wrote: > > > +++ b/man/systemd-run.xml > > @@ -215,7 +215,7 @@ along with systemd; If not, see > > . > > > > > > A

Re: [systemd-devel] Poor man's reboot doesn't work

Hi On Sun, Nov 2, 2014 at 12:48 PM, Thomas Meyer wrote: > Hi, > > I tried to switch to the emergency target and back to the graphical target, > but this doesn't seem to work. > > Should this work, i.e.? > > # systemctl isolate emergency.target > # systemctl isolate graphical.target > > The servic

Re: [systemd-devel] [PATCH] smack: introduce new SmackLabelExec option

On 11/07/2014 03:30 AM, Lennart Poettering wrote: > On Fri, 07.11.14 03:18, WaLyong Cho (walyong@gmail.com) wrote: > >> On 11/06/2014 11:54 PM, Lennart Poettering wrote: >>> On Tue, 04.11.14 17:35, WaLyong Cho (walyong@samsung.com) wrote: >>> In case of systemd has "_" label and run a

Re: [systemd-devel] Leak mempool/hashmap

2014-11-06 19:59 GMT+01:00 Jan Janssen : Hi, > > > On 2014-11-06 19:05, Lennart Poettering wrote: >> >> On Thu, 06.11.14 18:36, Jan Janssen (medhe...@web.de) wrote: >> >>> Hi, >>> >>> I just noticed that mempool/hashmap leaks memory. It's as simple as this >>> to >>> trigger: >>> >>> #include "has

Re: [systemd-devel] [systemd-commits] src/shared

On Thu, 06.11.14 15:30, Lennart Poettering (lenn...@poettering.net) wrote: > On Thu, 06.11.14 06:28, Harald Hoyer (har...@kemper.freedesktop.org) wrote: > > > > > Not all switch roots are like base_filesystem_create() wants them > > to look like. They might even boot, if they are RO

Re: [systemd-devel] Leak mempool/hashmap

On 2014-11-06 19:05, Lennart Poettering wrote: On Thu, 06.11.14 18:36, Jan Janssen (medhe...@web.de) wrote: Hi, I just noticed that mempool/hashmap leaks memory. It's as simple as this to trigger: #include "hashmap.h" int main(int argc, const char *argv[]) { Hashmap *m = hashmap_ne

Re: [systemd-devel] Udev rules hardware database

On Wed, 05.11.14 16:55, Patrick Häcker (pa...@web.de) wrote: heya, > sorry if this list is not the correct one for my post. In this case please > just point me to the correct list. It is the correct list. > I you want to have permanent power saving activated for your devices, the > recommende

Re: [systemd-devel] [PATCH] bus-proxy: cloning smack label

On Thu, 06.11.14 11:44, Przemyslaw Kedzierski (p.kedzier...@samsung.com) wrote: > When dbus client connects to systemd-bus-proxyd through > Unix domain socket proxy takes client's smack label and sets for itself. > > It is done before and independent of dropping privileges. > > The reason of suc

Re: [systemd-devel] [PATCH] smack: introduce new SmackLabelExec option

On Fri, 07.11.14 03:18, WaLyong Cho (walyong@gmail.com) wrote: > On 11/06/2014 11:54 PM, Lennart Poettering wrote: > > On Tue, 04.11.14 17:35, WaLyong Cho (walyong@samsung.com) wrote: > > > >> In case of systemd has "_" label and run as root, if a service file > >> has "User=" option and

Re: [systemd-devel] [PATCH] smack: introduce new SmackLabelExec option

On 11/06/2014 11:54 PM, Lennart Poettering wrote: > On Tue, 04.11.14 17:35, WaLyong Cho (walyong@samsung.com) wrote: > >> In case of systemd has "_" label and run as root, if a service file >> has "User=" option and the command line file has a special SMACK label >> then systemd will fail to e

Re: [systemd-devel] Poor man's reboot doesn't work

> Am 04.11.2014 um 20:01 schrieb Thomas Meyer : > > >> Am 02.11.2014 um 12:48 schrieb Thomas Meyer : >> >> Hi, >> >> I tried to switch to the emergency target and back to the graphical target, >> but this doesn't seem to work. >> >> Should this work, i.e.? Can anybody answer my question? Or

Re: [systemd-devel] Leak mempool/hashmap

On Thu, 06.11.14 18:36, Jan Janssen (medhe...@web.de) wrote: > Hi, > > I just noticed that mempool/hashmap leaks memory. It's as simple as this to > trigger: > > #include "hashmap.h" > int main(int argc, const char *argv[]) { > Hashmap *m = hashmap_new(&string_hash_ops); > hashma

[systemd-devel] Leak mempool/hashmap

Hi, I just noticed that mempool/hashmap leaks memory. It's as simple as this to trigger: #include "hashmap.h" int main(int argc, const char *argv[]) { Hashmap *m = hashmap_new(&string_hash_ops); hashmap_free(m); } ___ systemd-devel ma

Re: [systemd-devel] systemd-machined sigterm, cgroups trimmed

On Tue, 04.11.14 08:38, Major Hayden (ma...@mhtx.net) wrote: > Hello there, > > I'm currently running systemd 216 on Fedora 21 and I've found an issue where > systemd-machined stops running and cgroups are trimmed from the scope of > running qemu virtual machines. The series of events looks li

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

Simon McVittie wrote on 06/11/14 15:21: > On 06/11/14 14:16, Zbigniew Jędrzejewski-Szmek wrote: >> > What matters is how it is all arranged: >> > >> > - if there's a job that does stuff, and then calls reboot or shutdown >> > - a hook into the shutdown or reboot target does some work > unattended-

[systemd-devel] segfault in timesyncd

Here are the logs: Nov 06 16:14:56 numenor systemd[1]: Started Network Time Synchronization. Nov 06 16:14:56 numenor systemd-timesyncd[4881]: Using NTP server 10.3.255.254:123 (10.3.255.254). Nov 06 16:15:06 numenor systemd-timesyncd[4881]: Timed out waiting for reply from 10.3.255.254:123 (10.3

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On Thu, Nov 06, 2014 at 03:21:33PM +, Simon McVittie wrote: > On 06/11/14 14:16, Zbigniew Jędrzejewski-Szmek wrote: > > What matters is how it is all arranged: > > > > - if there's a job that does stuff, and then calls reboot or shutdown > > - a hook into the shutdown or reboot target does som

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On 06/11/14 14:16, Zbigniew Jędrzejewski-Szmek wrote: > What matters is how it is all arranged: > > - if there's a job that does stuff, and then calls reboot or shutdown > - a hook into the shutdown or reboot target does some work unattended-upgrades is currently the latter: the user shuts down (

Re: [systemd-devel] does poweroff -f really sync

On Thu, Nov 06, 2014 at 03:22:50PM +0100, Lennart Poettering wrote: > On Thu, 06.11.14 15:08, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > On a related note: if I read the code correctly, reboot -f or > > JobFailureAction=reboot-force should sync the filesystems. But this doesn't >

Re: [systemd-devel] [PATCH] hostnamed: add chassis type "robot"

Yes, In our use case (and prolly likewise in a lot of embedded use cases) there is another layer that provides more info on what kind of robot it is. So we are not using this variable for anything other than setting it right now, and "embedded" sounds good indeed. Thanks, Noé. 2014-11-06 14:39

Re: [systemd-devel] So how am I supposed to put together my Linux system?

On 09.09.2014 17:01, Colin Guthrie wrote: > Tobias Hunger wrote on 05/09/14 19:34: >> Any place that you would care to recomend? It would suck to have each >> distro put kernels somewhere else. > > Good question. > > On Mageia and Fedora (at least originally, not sure if it's changed > recently),

Re: [systemd-devel] [PATCH] smack: introduce new SmackLabelExec option

On Tue, 04.11.14 17:35, WaLyong Cho (walyong@samsung.com) wrote: > In case of systemd has "_" label and run as root, if a service file > has "User=" option and the command line file has a special SMACK label > then systemd will fail to execute the command. Generally, SMACK label > is ignored f

Re: [systemd-devel] So how am I supposed to put together my Linux system?

On 22.10.2014 21:08, Tobias Hunger wrote: > Hi Lennart, > > On Wed, Oct 22, 2014 at 7:03 PM, Lennart Poettering > wrote: >> Sorry for the late response, been travelling for a month, and then >> have been more travelling, and still trying to process all the mails >> that queued up since. > > No p

Re: [systemd-devel] [systemd-commits] src/shared

On Thu, 06.11.14 06:28, Harald Hoyer (har...@kemper.freedesktop.org) wrote: > > Not all switch roots are like base_filesystem_create() wants them > to look like. They might even boot, if they are RO and don't have the FS > layout. Just ignore the error and switch_root nevertheless

Re: [systemd-devel] [PATCH] s/commandline/command line/g

On Wed, 05.11.14 14:56, har...@redhat.com (har...@redhat.com) wrote: > +++ b/man/systemd-run.xml > @@ -215,7 +215,7 @@ along with systemd; If not, see > . > > > All command-line arguments after the first non-option > -argument become part of the comm

Re: [systemd-devel] [PATCH] switch_root: do not fail, if base_filesystem_create() failed

On 04.11.2014 19:17, Daniel Buch wrote: > I think you might want to cast it to avoid compiler warning. Like: > (void) base_filesystem_create() > > Den 04/11/2014 17.36 skrev mailto:har...@redhat.com>>: > > From: Harald Hoyer mailto:har...@redhat.com>> > > Not all switch roots are like ba

Re: [systemd-devel] [PATCH] s/commandline/command line/g

On 05.11.2014 14:56, har...@redhat.com wrote: > From: Harald Hoyer > > --- > TODO | 2 +- > m4/attributes.m4 | 2 +- > man/systemd-bootchart.xml | 4 ++-- > man/systemd-delta.xml | 2 +- > man/s

Re: [systemd-devel] does poweroff -f really sync

On Thu, 06.11.14 15:08, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > On a related note: if I read the code correctly, reboot -f or > JobFailureAction=reboot-force should sync the filesystems. But this doesn't > seem to work: > - on fedora-devel Adam W. said that fsck ran after a boot t

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On Thu, Nov 06, 2014 at 02:12:52PM +, "Jóhann B. Guðmundsson" wrote: > > On 11/06/2014 01:28 PM, Lennart Poettering wrote: > >However, doing unattended upgrades at shutdown is not really a > >common case. > > > Well for Debian and Debian based distribution it most certainly can > be the case

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On 11/06/2014 01:28 PM, Lennart Poettering wrote: However, doing unattended upgrades at shutdown is not really a common case. Well for Debian and Debian based distribution it most certainly can be the case since it has allowed for it's update/upgrade mechanism to be configured to install up

[systemd-devel] does poweroff -f really sync

On a related note: if I read the code correctly, reboot -f or JobFailureAction=reboot-force should sync the filesystems. But this doesn't seem to work: - on fedora-devel Adam W. said that fsck ran after a boot timeout - yesterday I did something like 'sudo install ./systemd /usr/lib/systemd/ && su

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On Thu, Nov 06, 2014 at 02:28:12PM +0100, Lennart Poettering wrote: > On Thu, 06.11.14 12:45, Patrick Häcker (pa...@web.de) wrote: > > > > > However, this one appears bogus to me. Is there any such software > > > > around that really does this? And if so, this really appears weird to > > > > me to

Re: [systemd-devel] [PATCH] hostnamed: add chassis type "robot"

On Thu, 06.11.14 14:34, Lennart Poettering (lenn...@poettering.net) wrote: > On Thu, 06.11.14 06:34, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > On Wed, Nov 05, 2014 at 06:40:51PM +0100, Noé Rubinstein wrote: > > > --- > > > man/hostnamectl.xml | 3 ++- > > > man/m

Re: [systemd-devel] [PATCH] hostnamed: add chassis type "robot"

On Thu, 06.11.14 06:34, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > On Wed, Nov 05, 2014 at 06:40:51PM +0100, Noé Rubinstein wrote: > > --- > > man/hostnamectl.xml | 3 ++- > > man/machine-info.xml | 3 ++- > > shell-completion/bash/hostnamectl | 2 +- > >

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On Thu, 06.11.14 12:45, Patrick Häcker (pa...@web.de) wrote: > > > However, this one appears bogus to me. Is there any such software > > > around that really does this? And if so, this really appears weird to > > > me to support. Delaying shutdown for more than 30min is just wrong. > > Isn't this

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On Thu, Nov 06, 2014 at 12:48:23PM +0100, Lennart Poettering wrote: > On Thu, 06.11.14 06:52, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > > > On shutdown there might be other jobs, like downloading of updates > > > > for > > > > installation, and other custom jobs. It see

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

> > However, this one appears bogus to me. Is there any such software > > around that really does this? And if so, this really appears weird to > > me to support. Delaying shutdown for more than 30min is just wrong. > Isn't this what the various "download updates and reboot" gnome-y > things are do

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

On Thu, 06.11.14 06:52, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > On shutdown there might be other jobs, like downloading of updates for > > > installation, and other custom jobs. It seems better to schedule an > > > individual timeout on each one separately, when it

[systemd-devel] [PATCH] bus-proxy: cloning smack label

When dbus client connects to systemd-bus-proxyd through Unix domain socket proxy takes client's smack label and sets for itself. It is done before and independent of dropping privileges. The reason of such soluton is fact that tests of access rights performed by lsm may take place inside kernel,

Re: [systemd-devel] [PATCH] rules: rerun vconsole-setup when switching from vgacon to fbcon

Hi Ray On Thu, Nov 6, 2014 at 10:40 AM, David Herrmann wrote: > On Wed, Nov 5, 2014 at 4:11 PM, Ray Strode wrote: >>> So if you have no idea how to make that rule be generated only if >>> ENABLE_VCONSOLE is set by configure, then we probably should take my >>> patch below. >> Your patch seems fa

[systemd-devel] [PATCH] shared/install: don't report 'static' when unit contains only Also=

If a unit contains only Also=, with no Alias= or WantedBy=, it shouldn't be reported as static. If any target unit specified in Also= is enabled or disabled, report this unit as enabled or disabled as well. https://bugzilla.redhat.com/show_bug.cgi?id=864298 --- src/shared/install.c | 23 +

[systemd-devel] [PATCH] shared/install: don't report 'static' when unit contains only Also=

I think that this patch might be a bit ineffective, as it calls unit_file_load() again just to get an InstallContext. I wasn't sure how to get Also= targets in any other way. If such change makes sense, this patch should probably be considered a preview rather than something to be committed right

Re: [systemd-devel] [PATCH] rules: rerun vconsole-setup when switching from vgacon to fbcon

Hi On Wed, Nov 5, 2014 at 4:11 PM, Ray Strode wrote: > Hi, > > On Wed, Nov 5, 2014 at 9:53 AM, David Herrmann wrote: >> I had that change locally, but didn't push it because vconsole is >> optional. Thus, this rule must be optional, too. I'm now digging into >> autoconf+m4 to see how to do this.

Re: [systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

Zbigniew Jędrzejewski-Szmek wrote on 06/11/14 05:52: >> > However, this one appears bogus to me. Is there any such software >> > around that really does this? And if so, this really appears weird to >> > me to support. Delaying shutdown for more than 30min is just wrong. > Isn't this what the vario