[systemd-devel] systemd boot sequence doubt

2015-10-21 Thread kennedy
what is systemd booting sequence? how is Systemd support both sysV's runlevel script and systemd's target file at the same time? I define the sysV runlevel script, and add it into /etc/rc5.d/ and I define another systemd target file, and use systemctl enable it. both of them could work fine.

Re: [systemd-devel] backlight service stopped at boot

2015-10-21 Thread Vlad
Thanks for the explanation. I'll try 227 asap. Vladimir. On 20/10/15 12:19, Lennart Poettering wrote: > On Tue, 20.10.15 08:21, Vlad (vo...@vovan.nl) wrote: > >> Hello, >> >> On my laptop the backlight service is stopped at boot instead of starting: >> >> # journalctl -a -b | grep backl >> Oct 20

Re: [systemd-devel] list-units with more than one argument

2015-10-21 Thread Lennart Poettering
On Tue, 20.10.15 13:27, Johannes Ernst (johannes.er...@gmail.com) wrote: > systemctl list-units foo.service bar.service > produces > Too many arguments. > now in 227. This used to work in 226. Apparently only one argument is allowed > now? Is that intended? (I prefer not.) Nope, not intended. I

Re: [systemd-devel] logger --id=val is ignored by systemd

2015-10-21 Thread Lennart Poettering
On Wed, 21.10.15 10:05, Olaf Hering (o...@aepfle.de) wrote: > How can scripts which use "logger -t id --id=val" get "me[val]" into syslog? > This used to work, with a systemd based system it looks like this: > > root@probook:~ # journalctl -f & > root@probook:~ # logger -t "me" --no-act --stderr

Re: [systemd-devel] 208 VS 219

2015-10-21 Thread Lennart Poettering
On Wed, 21.10.15 09:29, yan...@iscas.ac.cn (yan...@iscas.ac.cn) wrote: > > hello guys,Systemd 208 VS Systemd219 ,Do they have many changes that can > improve boot time?? Thank you! See https://raw.githubusercontent.com/systemd/systemd/master/NEWS for information on the changes made. We gene

Re: [systemd-devel] systemd blog page little bug

2015-10-21 Thread Colin Guthrie
kennedy wrote on 21/10/15 08:23: > reference http://0pointer.de/blog/projects/systemd-for-admins-3.html > > In this blog > > " > Note that a dependency of type After= only encodes the suggested > ordering, but does not actually cause syslog to be started when abrtd is > -- and this is exactly wh

[systemd-devel] logger --id=val is ignored by systemd

2015-10-21 Thread Olaf Hering
How can scripts which use "logger -t id --id=val" get "me[val]" into syslog? This used to work, with a systemd based system it looks like this: root@probook:~ # journalctl -f & root@probook:~ # logger -t "me" --no-act --stderr --id=$PPID "foo: blah" <13>Oct 21 09:58:11 me[2606]: foo: blah root@pr

[systemd-devel] systemd blog page little bug

2015-10-21 Thread kennedy
reference http://0pointer.de/blog/projects/systemd-for-admins-3.html In this blog " Note that a dependency of type After= only encodes the suggested ordering, but does not actually cause syslog to be started when abrtd is -- and this is exactly what we want, since abrtd actually works fine e