Re: [systemd-devel] v19: plymouth-quit-wait waits forever/no getty

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 10:58, Andrey Borzenkov ([email protected]) wrote: > 2) getty's now are ordered after plymouth-quit-wait, so they are never > started until plymouth --wait finishes. But it never finishes because > plymouth-quit is never run. Unfortunately, TimeoutSec is not applied > to oneshot

Re: [systemd-devel] rc-local.service ordering

2011-03-01 Thread Lennart Poettering
On Wed, 02.03.11 00:07, Andrey Borzenkov ([email protected]) wrote: > Have you actually read what I wrote? > > "Now, I do not care much about rc-sysinit itself. But I do care that > services that we want to be started late are *really* started late." > > Currently I have impression that rc-loc

Re: [systemd-devel] %post %preun rpm macros

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 14:38, Alexey Shabalin ([email protected]) wrote: Heya, > "condrestart" equivalent to a "try-restart" As you found out this alias already exists. > "condreload" may be like "reload-or-try-restart" Added this alias now for you. > Is it possible to add aliase for "condrestar

Re: [systemd-devel] rc-local.service ordering

2011-03-01 Thread Andrey Borzenkov
On Tue, Mar 1, 2011 at 11:57 PM, Matthew Miller wrote: > On Tue, Mar 01, 2011 at 09:47:14PM +0100, Lennart Poettering wrote: >> I think the rc-local is a broken concept: the semantics of having a >> service running after everything else are just broken, and usually just >> something people want to

Re: [systemd-devel] rc-local.service ordering

2011-03-01 Thread Matthew Miller
On Tue, Mar 01, 2011 at 09:47:14PM +0100, Lennart Poettering wrote: > I think the rc-local is a broken concept: the semantics of having a > service running after everything else are just broken, and usually just > something people want to do to avoid thinking about ordering. Yes! Sysadmins who w

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 23:39, Andrey Borzenkov ([email protected]) wrote: > > On Tue, Mar 1, 2011 at 12:32 AM, Lennart Poettering > wrote: > > > > if we merge this, is SysVConsole still useful then? Shouldn't we kill > > that then? > > > > Killing existing option is not easy. Good package manager w

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 23:36, Andrey Borzenkov ([email protected]) wrote: > > On Tue, Mar 1, 2011 at 10:51 PM, Lennart Poettering > wrote: > >> > The only problem with that > >> > I see is that syslog implementations started with sysv scripts would end > >> > up in a cyclic loop, and I don't know ho

Re: [systemd-devel] rc-local.service ordering

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 10:34, Andrey Borzenkov ([email protected]) wrote: > Historically rc.local was supposed to be run very late (last) in > startup sequence; and systemd implicitly relies on it (at least, on > fedora-like systems) implicitly ordering many things "to be done late" > afetr rc-sysinit

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Andrey Borzenkov
On Tue, Mar 1, 2011 at 12:32 AM, Lennart Poettering wrote: > > if we merge this, is SysVConsole still useful then? Shouldn't we kill > that then? > Killing existing option is not easy. Good package manager will try to reexec systemd and it will pass no more existing option to new instance which w

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Andrey Borzenkov
On Tue, Mar 1, 2011 at 10:51 PM, Lennart Poettering wrote: >> > The only problem with that >> > I see is that syslog implementations started with sysv scripts would end >> > up in a cyclic loop, and I don't know how to fix this... >> > >> >> Could you elaborate? Do you mean messages may be echoed

Re: [systemd-devel] JobTimeout

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 07:32, Andrey Borzenkov ([email protected]) wrote: > Could someone please give example of intended usage? I must admit I do > not really understand it from reading documentation. Thank you! JobTimeout= adds a timeout to jobs enqueued for a unit. If a job is queued for longer th

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 22:37, Andrey Borzenkov ([email protected]) wrote: > > How are you planning to use this? connect stdout of all services to > > /dev/null, and stderr to syslog? I guess such a default configuration > > coming from upstream might make sense: that way all errors would go to > > sys

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Andrey Borzenkov
On Tue, Mar 1, 2011 at 10:07 PM, Lennart Poettering wrote: > On Tue, 01.03.11 11:04, Andrey Borzenkov ([email protected]) wrote: > >> > Hmm, how would you use this? Send SysV stdout to /dev/null, but SysV >> > stderr to the console? Is this really advisable? i.e. are you sure that >> > if curren

Re: [systemd-devel] Service unit file submission: fcron.service

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 15:26, Pablo Hess ([email protected]) wrote: > [Unit] > Description=fcron Cron Daemon > Wants=syslog.target Wants? I'd guess fcron works fine if syslog is not around, right? Hence Wants= is not really necessary. However, you want to make sure that fcron is started after the

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Lennart Poettering
On Tue, 01.03.11 11:04, Andrey Borzenkov ([email protected]) wrote: > > Hmm, how would you use this? Send SysV stdout to /dev/null, but SysV > > stderr to the console? Is this really advisable? i.e. are you sure that > > if current init scripts encounter an error they properly write warnings > >

Re: [systemd-devel] Service unit file submission: fcron.service

2011-03-01 Thread Andrey Borzenkov
On Tue, Mar 1, 2011 at 9:26 PM, Pablo Hess wrote: > Hey, I'd like to contribute this service file I've created for the fcron > cron-like daemon. > > I looked for something similar but found nothing so far. > > > > [Unit] > Description=fcron Cron Daemon > Wants=syslog.target Does it really need to

[systemd-devel] Service unit file submission: fcron.service

2011-03-01 Thread Pablo Hess
Hey, I'd like to contribute this service file I've created for the fcron cron-like daemon. I looked for something similar but found nothing so far. [Unit] Description=fcron Cron Daemon Wants=syslog.target [Service] Type=forking ExecStart=/usr/sbin/fcron ExecReload=/bin/kill -USR1 $MAINPID Exec

Re: [systemd-devel] %post %preun rpm macros

2011-03-01 Thread Alexey Shabalin
> "condrestart" equivalent to a "try-restart" > "condreload" may be like "reload-or-try-restart" > Is it possible to add alias for "condrestart" to "try-restart"? and Sorry, i see this alias exist. Thank you. > "condreload" to "reload-or-try-restart"? > What use for "condstop"? May be "stop"? -

[systemd-devel] %post %preun rpm macros

2011-03-01 Thread Alexey Shabalin
Hello. We use macroses for %post and %preun in rpm in our distributive(ALTLinux). Like: %post %post_service %name %preun %preun_service %name %*_service is script - "/sbin/chkconfig --add" for install package - "/sbin/chkconfig "$1" resetpriorities"+"/sbin/service "$1" condrestart" for upgrade pa

Re: [systemd-devel] v19: plymouth-quit-wait waits forever/no getty

2011-03-01 Thread Andrey Borzenkov
On Tue, Mar 1, 2011 at 10:58 AM, Andrey Borzenkov wrote: > 1) plymouth-quit is not ever started. I do not understand why - it is > queued, and it should be started after rc-local.service is finished > and it is not. Log attached. > Forget this. I had plymouth-quit with local modification in this

Re: [systemd-devel] [PATCH] allow explicit stdout/stderr configuration for SysV services

2011-03-01 Thread Andrey Borzenkov
On Tue, Mar 1, 2011 at 12:32 AM, Lennart Poettering wrote: > On Sun, 27.02.11 01:05, Andrey Borzenkov ([email protected]) wrote: > >> Currently it is possible to either output legacy initscripts on >> console which often messes it up completely, or suppress output >> alltogether which makes it h