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

On 11/11/2014 04:10 AM, Lennart Poettering wrote: > On Tue, 11.11.14 00:43, WaLyong Cho (walyong@samsung.com) wrote: > >> On 11/10/2014 10:26 PM, Lennart Poettering wrote: >>> On Fri, 07.11.14 10:03, Casey Schaufler (ca...@schaufler-ca.com) wrote: >>> Calling it SmackLabel= instead of Sma

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

On Mon, Nov 10, 2014 at 10:53:46PM +0100, Lennart Poettering wrote: > On Thu, 06.11.14 14:44, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > 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: > > > >

Re: [systemd-devel] 'systemctl poweroff' no longer shuts down system -- instead, reboots ?

On Mon, Nov 10, 2014 at 04:22:42PM -0800, grantksupp...@operamail.com wrote: > On Mon, Nov 10, 2014, at 04:07 PM, Lennart Poettering wrote: > > On Thu, 30.10.14 12:30, grantksupp...@operamail.com > > (grantksupp...@operamail.com) wrote: > > > > > exec of > > > > > > systemctl poweroff > > > >

Re: [systemd-devel] Shutdown problems

Lennart Poettering writes: > On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: > >> > Please boot with "systemd.log_level=debug", then make the machine hang >> > and check what the last things in the logs say. Maybe then paste that >> > somewhere online and post the URL for that her

Re: [systemd-devel] 'systemctl poweroff' no longer shuts down system -- instead, reboots ?

On Mon, Nov 10, 2014, at 04:07 PM, Lennart Poettering wrote: > On Thu, 30.10.14 12:30, grantksupp...@operamail.com > (grantksupp...@operamail.com) wrote: > > > exec of > > > > systemctl poweroff > > > > causes, as reported, a reboot/restart > > > > but, exec of > > > > systemctl --force p

Re: [systemd-devel] [PATCH] Add timesync-wait tool

On Wed, 29.10.14 17:50, Lukasz Stelmach (stl...@poczta.fm) wrote: > > I mean, what is the tool supposed to be > > waiting on: that the time is set as accurately as possible (in that > > case watching STA_UNSYNC sounds good, plus waiting for > > TFD_CANCEL_ON_SET for big jumps and guessing sleep ti

Re: [systemd-devel] Commands started after "su - username" do not obey "systemctl set-property user.slice MemoryLimit=..."

On Wed, 29.10.14 21:08, Lutz Vieweg (l...@5t9.de) wrote: > Hi, > > I configured a CentOS 7 to limit the amount of memory any single > interactive user can use by setting: > > >systemctl set-property user.slice MemoryLimit=60G > > and excepted "root" to use a less strict limit: > > >systemctl s

Re: [systemd-devel] 'systemctl poweroff' no longer shuts down system -- instead, reboots ?

On Thu, 30.10.14 12:30, grantksupp...@operamail.com (grantksupp...@operamail.com) wrote: > exec of > > systemctl poweroff > > causes, as reported, a reboot/restart > > but, exec of > > systemctl --force poweroff > > otoh, does shut down the machine, though not gracefully This got recent

Re: [systemd-devel] [PATCH 5/5] calendar: parse months's names

On Thu, 30.10.14 12:19, Daniele Medri (dme...@gmail.com) wrote: As mentiond in my early review, such a bitfield would duplicate the "months" chain we already have in place. I am totally onboard with allowing a syntax where month names are used, but this really should be translated into the normal

Re: [systemd-devel] [PATCH 2/5] man: reorganization of calendar specs

On Thu, 30.10.14 12:19, Daniele Medri (dme...@gmail.com) wrote: > --- > man/systemd.time.xml | 31 ++- > 1 file changed, 14 insertions(+), 17 deletions(-) > > diff --git a/man/systemd.time.xml b/man/systemd.time.xml > index 2342684..2ee5858 100644 > --- a/man/systemd.

Re: [systemd-devel] [PATCH 1/5] calendar: semesterly alias for semi-annually

On Thu, 30.10.14 12:19, Daniele Medri (dme...@gmail.com) wrote: I am still not convinced that "semesterly" is really a good addition. See previous comments about that: I am a bit conservative about that. "Semester" has a very academic touch to it, and at least in germany the s

Re: [systemd-devel] [PATCH] localed: validate set-x11-keymap input

On Tue, 04.11.14 12:05, Jan Synacek (jsyna...@redhat.com) wrote: One more addition: > +} > + > +int xkb_get_keymaps(char ***list, enum keymap_state look_for, const char > *layout_prefix) > +{ > +_cleanup_fclose_ FILE *f; > +char line[LINE_MAX]; > +enum keymap_state state

Re: [systemd-devel] [PATCH] localed: validate set-x11-keymap input

On Tue, 04.11.14 12:05, Jan Synacek (jsyna...@redhat.com) wrote: > diff --git a/src/locale/localectl.c b/src/locale/localectl.c > index d4a2d29..8f9e4da 100644 > --- a/src/locale/localectl.c > +++ b/src/locale/localectl.c > @@ -46,6 +46,7 @@ > #include "virt.h" > #include "fileio.h" > #include

Re: [systemd-devel] [PATCHv6] tmpfiles, man: Add xattr support to tmpfiles

On Thu, 30.10.14 12:21, Maciej Wereski (m.were...@partner.samsung.com) wrote: > > +static int get_xattrs_from_arg(Item *i) { > +_cleanup_free_ char *xattr = NULL; > +const char *p; > +int n; > + > +assert(i); > +if (i->type != SET_XATTR) > +

Re: [systemd-devel] Service not restarting after Condition failed

On Thu, 30.10.14 18:47, D.S. Ljungmark (spi...@aanstoot.se) wrote: > Hi > we have a service set to: > ConditionFileNotEmpty= > > and > > Restart=Always > > > This combination would (in my feebled mind) cause the service to restart > once the Condition was fulfilled, but that doesn't seem to b

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

On Mon, 10.11.14 22:30, Thomas Meyer (tho...@m3y3r.de) wrote: > Am Freitag, den 07.11.2014, 01:59 +0100 schrieb Lennart Poettering: > > 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 > >

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

On Thu, 06.11.14 14:44, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > 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 > >

Re: [systemd-devel] Should systemd-logind provide a DM-independent mechanism for handling guest accounts?

On Mon, 10.11.14 16:41, Laércio de Sousa (laercioso...@sme-mogidascruzes.sp.gov.br) wrote: > Hi there! > > Currently there are few alternatives for implementing guest accounts in > Linux systems. I know only two: an AppArmor-based approach implemented in > LightDM, and a SELinux-based approach i

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

Am Freitag, den 07.11.2014, 01:59 +0100 schrieb Lennart Poettering: > 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.? > >

Re: [systemd-devel] udevd and "quiet"

Lennart Poettering wrote on 10/11/14 18:54: > On Mon, 10.11.14 10:11, Colin Guthrie (gm...@colin.guthr.ie) wrote: > >> Hi, >> >> Not sure how long this has been the case, but in a dracut initrd that is >> NOT using systemd, udevd will print out "starting version 217" even when >> "quiet" is used o

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

On Thu, Nov 6, 2014 at 9:37 AM, Lennart Poettering 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 >> . >> >> >> All command-line arguments

Re: [systemd-devel] user environment variables

>> As for the variable, two more wishes (not a big deal yet): >> - in units, why not add a specifier reflecting $XDG_CONFIG_HOME > > Hmm, when we start with that, then I figure people want the other XDG > dirs as well, soon... > > Anyway, what's the usecase for this? Just laziness when writing ser

Re: [systemd-devel] generator logging during daemon-reload

On Mon, 10.11.14 20:30, Alexandre Detiste (alexandre.deti...@gmail.com) wrote: > >> Yes, but then the log appears as a ugly big chunck without the > >> timestamp & host on the left; > > > except the first line. Is it ok to reopen /dev/ksmg for each line > > > writen to avoid this ? > > > > Not s

Re: [systemd-devel] Shutdown problems

On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: > > Please boot with "systemd.log_level=debug", then make the machine hang > > and check what the last things in the logs say. Maybe then paste that > > somewhere online and post the URL for that here, so that we can have a > > look.

Re: [systemd-devel] generator logging during daemon-reload

>> Yes, but then the log appears as a ugly big chunck without the >> timestamp & host on the left; > > except the first line. Is it ok to reopen /dev/ksmg for each line > > writen to avoid this ? > > Not sure I follow? This might be a trivial problem; it's just that there are really few people w

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

On Thu, 06.11.14 16:59, Colin Guthrie (gm...@colin.guthr.ie) wrote: > 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 shutdow

Re: [systemd-devel] user environment variables

On Fri, 07.11.14 20:40, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > > > We could probably at least open up DefaultEnvironment= to specifier > > expansion, so that %t would work the same way as in unit files. I > > added a TODO list item for this now. > > > > Thank you so much < This

Re: [systemd-devel] [PATCH] shared: explicitly ignore the return value of wait_for_terminate

On Sun, 09.11.14 15:51, Ronny Chevalier (chevalier.ro...@gmail.com) wrote: > CID#1237532 > CID#1237523 > CID#1237522 Applied! Thanks! Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lis

Re: [systemd-devel] [PATCH v2] shared/install: when unit contains only Also=, report 'indirect'

On Fri, 07.11.14 21:21, Jan Synacek (jsyna...@redhat.com) wrote: > If a unit contains only Also=, with no Alias= or WantedBy=, it shouldn't > be reported as static. New 'indirect' status shall be introduced. Thanks! Applied! (Made one more commit afterwards changing the description of the new un

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

On Tue, 11.11.14 00:43, WaLyong Cho (walyong@samsung.com) wrote: > On 11/10/2014 10:26 PM, Lennart Poettering wrote: > > On Fri, 07.11.14 10:03, Casey Schaufler (ca...@schaufler-ca.com) wrote: > > > >> Calling it SmackLabel= instead of SmackLabelExec= would be fine as > >> far as I'm concerne

Re: [systemd-devel] udevd and "quiet"

On Mon, 10.11.14 10:11, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Hi, > > Not sure how long this has been the case, but in a dracut initrd that is > NOT using systemd, udevd will print out "starting version 217" even when > "quiet" is used on the command line. Hmm, that message is printed at

Re: [systemd-devel] generator logging during daemon-reload

On Mon, 10.11.14 17:38, Alexandre Detiste (alexandre.deti...@gmail.com) wrote: > Le lundi 10 novembre 2014, 14:32:49 Lennart Poettering a écrit : > > > I know that generators should log to /dev/kmsg during early boot. > > > > Correct! > > Yes, but then the log appears as a ugly big chunck withou

[systemd-devel] Should systemd-logind provide a DM-independent mechanism for handling guest accounts?

Hi there! Currently there are few alternatives for implementing guest accounts in Linux systems. I know only two: an AppArmor-based approach implemented in LightDM, and a SELinux-based approach implemented in Fedora's package "xguest" that works with GDM. There's no option for console guest login

Re: [systemd-devel] generator logging during daemon-reload

Le lundi 10 novembre 2014, 14:32:49 Lennart Poettering a écrit : > > I know that generators should log to /dev/kmsg during early boot. > > Correct! Yes, but then the log appears as a ugly big chunck without the timestamp & host on the left; except the first line. Is it ok to reopen /dev/ksmg fo

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

On 11/10/2014 10:26 PM, Lennart Poettering wrote: > On Fri, 07.11.14 10:03, Casey Schaufler (ca...@schaufler-ca.com) wrote: > >> Calling it SmackLabel= instead of SmackLabelExec= would be fine as >> far as I'm concerned. SmackLabel= is more consistent with SELinuxContext= >> and AppArmorProfile=,

Re: [systemd-devel] remount

On Fri, 07.11.14 15:35, Fisher, Charles J. (Top Echelon) (charles.fis...@alcoa.com) wrote: > When I start a container like this: > > [root@limsdev ~]# systemd-nspawn -bD /home/limsbox --bind-ro=/usr/lib64 > --bind-ro=/home/oracle/Ora12c/db > > Is there any way I can stop the container root fro

Re: [systemd-devel] generator logging during daemon-reload

On Fri, 07.11.14 20:59, Alexandre Detiste (alexandre.deti...@gmail.com) wrote: > Hi, > > I know that generators should log to /dev/kmsg during early boot. Correct! > But, when they are restarted later by systemcl daemon-reload; > is it better to write to the journal instead, by using systemd-ca

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

On Fri, 07.11.14 10:03, Casey Schaufler (ca...@schaufler-ca.com) wrote: > Calling it SmackLabel= instead of SmackLabelExec= would be fine as > far as I'm concerned. SmackLabel= is more consistent with SELinuxContext= > and AppArmorProfile=, as you point out. OK! WaLyong, let's name it SmackLabel

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

On 11/10/2014 08:57 PM, Simon McVittie wrote: > On 09/11/14 02:08, Casey Schaufler wrote: >> Thus, dbus is a fine example where SMACK64EXEC is a bad idea. Because you >> want a system bus and a user bus with different attributes you want it to get >> the Smack label at launch time, just like you do

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

On 09/11/14 02:08, Casey Schaufler wrote: > Thus, dbus is a fine example where SMACK64EXEC is a bad idea. Because you > want a system bus and a user bus with different attributes you want it to get > the Smack label at launch time, just like you do for UID and capability sets. I think there's a mu

Re: [systemd-devel] udevd and "quiet"

Sorry for the "speaking to myself" spam. Colin Guthrie wrote on 10/11/14 10:29: > Colin Guthrie wrote on 10/11/14 10:11: >> Hi, >> >> Not sure how long this has been the case, but in a dracut initrd that is >> NOT using systemd, udevd will print out "starting version 217" even when >> "quiet" is u

Re: [systemd-devel] udevd and "quiet"

Colin Guthrie wrote on 10/11/14 10:11: > Hi, > > Not sure how long this has been the case, but in a dracut initrd that is > NOT using systemd, udevd will print out "starting version 217" even when > "quiet" is used on the command line. > > This isn't ideal as it should be mostly silent when quiet

[systemd-devel] udevd and "quiet"

Hi, Not sure how long this has been the case, but in a dracut initrd that is NOT using systemd, udevd will print out "starting version 217" even when "quiet" is used on the command line. This isn't ideal as it should be mostly silent when quiet is used and indeed this is the only output from the

Re: [systemd-devel] [gummiboot][RFC] Add trusted boot (tboot) support to gummiboot

10.11.2014 14:10, Minchev, Todor wrote: Hello guys, I have been working on adding trusted boot (tboot) support to gummiboot and since this requires quite a bit of new code to be added to the gummiboot code base I wanted to send it out for review and comments. This is the new functionality that

[systemd-devel] [gummiboot][RFC] Add trusted boot (tboot) support to gummiboot

Hello guys, I have been working on adding trusted boot (tboot) support to gummiboot and since this requires quite a bit of new code to be added to the gummiboot code base I wanted to send it out for review and comments. This is the new functionality that these patches add to the gummiboot master