Hi,
If there is a foo.service which is required to run during first system
boot then what is the best solution to permanently disable it afterwards?
I can think of two solutions but I am not sure which one is correct/more
appropriate.
1) ExecStartPost=systemctl disable foo.service (I doubt
El 27/09/13 04:26, Muhammad Shakeel escribió:
Hi,
If there is a foo.service which is required to run during first system
boot then what is the best solution to permanently disable it afterwards?
I can think of two solutions but I am not sure which one is correct/more
appropriate.
1)
Hi,
On Fri, 2013-09-27 at 12:26 +0500, Muhammad Shakeel wrote:
If there is a foo.service which is required to run during first system
boot then what is the best solution to permanently disable it afterwards?
I can think of two solutions but I am not sure which one is correct/more
'Twas brillig, and Lennart Poettering at 26/09/13 19:35 did gyre and gimble:
On Thu, 26.09.13 15:46, Olav Vitters (o...@vitters.nl) wrote:
On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
(Of course, journald should not exit under any such circumstances, but
to find that
Hi,
I have noticed that ExecStop is not being run on following service
with following requests:
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/sh -c sleep 20 /usr/bin/systemd-cat echo ExecStart..
ExecStop=/bin/sh -c /usr/bin/systemd-cat echo ExecStop..
$ systemctl start
From: Michael Scherer m...@zarb.org
Seeing
http://www.happyassassin.net/2013/09/27/further-sysadmin-adventures-wheres-my-freeipa-badge/
it seems that the default message is a bit confusing for people
who never encountered it before, so adding a link to the manpage could
help them.
---
On Fri, Sep 27, 2013 at 11:43 AM, m...@zarb.org wrote:
From: Michael Scherer m...@zarb.org
Seeing
http://www.happyassassin.net/2013/09/27/further-sysadmin-adventures-wheres-my-freeipa-badge/
it seems that the default message is a bit confusing for people
who never encountered it before, so
On Wed, Sep 25, 2013 at 3:11 AM, Tim Landscheidt t...@tim-landscheidt.de
wrote:
on Fedora 19/systemd 204, I want systemd on mount
/mnt/test by a non-root user to automatically call a pro-
gram as root (in real life cryptsetup to unlock the underly-
ing device, for testing here echo) before
On Fri, 27.09.13 09:47, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Lennart Poettering at 26/09/13 19:35 did gyre and gimble:
On Thu, 26.09.13 15:46, Olav Vitters (o...@vitters.nl) wrote:
On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
(Of
On Fri, 27.09.13 12:26, Muhammad Shakeel (muhammad_shak...@mentor.com) wrote:
Hi,
If there is a foo.service which is required to run during first
system boot then what is the best solution to permanently disable it
afterwards?
I can think of two solutions but I am not sure which one is
It's also possible to create your own file system type. mount
(including via systemd mount units) simply invokes
/usr/sbin/mount.YOURTYPEHERE as root.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
This is an old thread from February. Sorry I can't reply to the original email.
Apparently I failed to notice this question. My bad.
Hello systemd developers
TL;DR: On a VT which X is running, messing with KDSKBMODE on
underneath X at best has no affect and at worst breaks keyboard input
Distributions such as openSUSE and probably others never included
upstart, in that case there is no need to include this code.
This introduces --disable-upstartcompat, however upstart compat is still
enabled by default.
---
configure.ac | 3 +++
src/systemctl/systemctl.c | 5 +
On Fri, Sep 27, 2013 at 9:24 PM, Cristian Rodríguez
crrodrig...@opensuse.org wrote:
Distributions such as openSUSE and probably others never included
upstart, in that case there is no need to include this code.
This introduces --disable-upstartcompat, however upstart compat is still
enabled
14 matches
Mail list logo
