Hello,
one of the most-requested features that is not present in systemd
currently is a true rc.local-type functionality that runs after all
other services.
I haven't read all past discussions, but from what I've gathered the
main objection from the systemd developers is that having a catch-all
On 09/27/2012 08:33 AM, Christian Seiler wrote:
one of the most-requested features that is not present in systemd
currently is a true rc.local-type functionality that runs after all
other services.
Any particular reason why those user just dont create type oneshot unit
then order it as they
Le jeudi 27 septembre 2012 à 11:07 +, Jóhann B. Guðmundsson a
écrit :
On 09/27/2012 08:33 AM, Christian Seiler wrote:
one of the most-requested features that is not present in systemd
currently is a true rc.local-type functionality that runs after all
other services.
Any particular
Am 27.09.2012 13:07, schrieb Jóhann B. Guðmundsson:
On 09/27/2012 08:33 AM, Christian Seiler wrote:
one of the most-requested features that is not present in systemd
currently is a true rc.local-type functionality that runs after all
other services.
Any particular reason why those user
'Twas brillig, and Henrik /KaarPoSoft at 26/09/12 22:51 did gyre and gimble:
Dear all,
journalctrl -b shows messages from the current boot.
However, I often find it useful to look at messages from the previous boot.
Hence I would like to propose a new feature:
journalctrl -b n
should
Am 27.09.2012 12:07, schrieb Jóhann B. Guðmundsson:
On 09/27/2012 08:33 AM, Christian Seiler wrote:
one of the most-requested features that is not present in systemd
currently is a true rc.local-type functionality that runs after all
other services.
Any particular reason why those user just
'Twas brillig, and Christian Seiler at 27/09/12 09:33 did gyre and gimble:
Hello,
one of the most-requested features that is not present in systemd
currently is a true rc.local-type functionality that runs after all
other services.
I haven't read all past discussions, but from what I've
I haven't read all past discussions, but from what I've gathered the
main objection from the systemd developers is that having a
catch-all
After=* dependency would not be the sane thing to do.
Can you just use a Type=idle unit?
From man systemd.service:
Behavior of idle is very similar to
If you want to run a script in the very end of everything you simply
order it after the default target as in
[Unit]
Description=My custom script
After=default.target
[Service]
Type=oneshot
ExecStart=/path/to/my/custom/script
[Install]
WantedBy=default.target
Hmmm, I remember vaguely that
On 09/27/2012 11:17 AM, Frederic Crozat wrote:
Le jeudi 27 septembre 2012 à 11:07 +, Jóhann B. Guðmundsson a
écrit :
On 09/27/2012 08:33 AM, Christian Seiler wrote:
one of the most-requested features that is not present in systemd
currently is a true rc.local-type functionality that runs
Le jeudi 27 septembre 2012 à 12:55 +, Jóhann B. Guðmundsson a
écrit :
On 09/27/2012 11:17 AM, Frederic Crozat wrote:
Le jeudi 27 septembre 2012 à 11:07 +, Jóhann B. Guðmundsson a
écrit :
On 09/27/2012 08:33 AM, Christian Seiler wrote:
one of the most-requested features that is not
On Thu, Sep 27, 2012 at 01:43:34PM +0100, Christian Seiler wrote:
The problem here is that a Type=idle service is basically a type=simple
service and you might want to have Type=forking or Type=oneshot
services
which you want to start.
Maybe sometimes like:
[Service]
Type=idle
2012/9/26 Lennart Poettering lenn...@poettering.net
Heya,
Almost exclusively only bug fixes. You want this if you are on 190 or
191 right now.
http://www.freedesktop.org/software/systemd/systemd-192.tar.xz
CHANGES WITH 192:
* The bash completion logic is now available for
It is no longer possible to manually enable systemd-udev-settle.service,
so its only use is by legacy services explicitly pulling it in. It makes
sense for these services to also explicitly order themselves after
udev-settle.service, which makes After=basic.target redundant.
This should reduce
On Thu, Sep 27, 2012 at 4:36 PM, Tom Gundersen t...@jklm.no wrote:
It is no longer possible to manually enable systemd-udev-settle.service,
so its only use is by legacy services explicitly pulling it in. It makes
sense for these services to also explicitly order themselves after
On Thu, 27.09.12 15:11, Mirco Tischler (mt...@gmx.de) wrote:
$systemd --version
systemd 191
$git grep 191 configure.ac
configure.ac:[191],
$git describe
v192
The version number didn't get the increment it deserves ;-)
Ah, bummer. I suck and fucked that up.
Will prep 193
On 09/27/12 01:22, Mirco Tischler wrote:
2012/9/27 Henrik /KaarPoSoft hen...@kaarposoft.dk:
On 09/27/12 00:05, Tom Gundersen wrote:
On Thu, Sep 27, 2012 at 12:02 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
(b) Is there a way to have logind NOT show a login prompt on VT1?
It is not
On Thu, Sep 27, 2012 at 7:28 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
Another problem is, that if I use
/etc/systemd/system/getty.target.wants/getty@tty2.service then
graphical.target may still put X11 on tty1, so the console messages are
hidden.
That should be configured/fixed in
Heya,
http://www.freedesktop.org/software/systemd/systemd-193.tar.xz
CHANGES WITH 193:
* journalctl gained a new --cursor= switch to show entries
starting from the specified location in the journal.
* We now enforce a size limit on journal entry fields exported
This occurrence of handle-sleep-key was overlooked when it was split.
See the attached patch.
0001-Update-systemd-inhibit-help-output.patch
Description: Binary data
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
20 matches
Mail list logo
