Greetings,
I am trying to learn to use systemd.
I scanned through some of the online manpages and looked at some example unit
files. I keep seeing
[Install]
WantedBy=multi-user.target
or
[Install]
WantedBy=sysinit.target
or some such
I have for example a need to mount stuff (via a mount
On Thu, Aug 01, 2013 at 07:48:19AM +0100, lux-integ wrote:
Greetings,
I am trying to learn to use systemd.
I scanned through some of the online manpages and looked at some example
unit
files. I keep seeing
[Install]
WantedBy=multi-user.target
or
[Install]
'Twas brillig, and WANG Chao at 01/08/13 06:36 did gyre and gimble:
On 07/30/13 at 04:40pm, Tom Gundersen wrote:
On Tue, Jul 30, 2013 at 4:13 PM, Harald Hoyer har...@redhat.com wrote:
On 07/30/2013 03:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
Maybe rootfsflags=nofail could do be used as this
[Resend because I fail at reply-all]
'Twas brillig, and WANG Chao at 01/08/13 06:36 did gyre and gimble:
On 07/30/13 at 04:40pm, Tom Gundersen wrote:
On Tue, Jul 30, 2013 at 4:13 PM, Harald Hoyer har...@redhat.com wrote:
On 07/30/2013 03:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
Maybe
On Wed, Jul 31, 2013 at 06:59:18PM +0100, lux-integ wrote:
On Wednesday 31 July 2013 14:22:35 Michal Vyskocil wrote:
You can split the logic into two mount units with opposite Condition
#mountpoint.mount
[Unit]
Description=mount mountpoint
ConditionPathIsMountPoint=/mountpoint
On 08/01/13 at 08:49am, Colin Guthrie wrote:
[Resend because I fail at reply-all]
'Twas brillig, and WANG Chao at 01/08/13 06:36 did gyre and gimble:
On 07/30/13 at 04:40pm, Tom Gundersen wrote:
On Tue, Jul 30, 2013 at 4:13 PM, Harald Hoyer har...@redhat.com wrote:
On 07/30/2013 03:46
On Thursday 01 August 2013 08:00:49 Tomasz Torcz wrote:
They cannot be in mount. There are few way to accomplish what you want,
but without details I can provide only vague directions. You need to
create unit for your work. You can stuff mkdir into ExecStartPre and cp
into ExecStart; you
From: Harald Hoyer har...@redhat.com
Since the journal can handle multiple lines just well natively,
and rsyslog can be configured to handle them as well, there is no need
to truncate messages from syslog() after the first newline.
Reproducer:
1. Add following four lines to /etc/rsyslog.conf
On Wednesday 31 July 2013 14:36:25 Colin Guthrie wrote:
Mount units have to be named specially after their mount points, so be
careful there e.g. if the mount point is /mnt/mymountpoint then the unit
should be called mnt-mymountpoint.mount
thanks for your reply
Now I have an init script to
On Thursday 01 August 2013 08:00:49 Tomasz Torcz wrote:
You can stuff mkdir into ExecStartPre and cp into ExecStart;
you have to make your unit Require the mount unit (or go with the
automounter); activation of your work unit should trigger mount.
many thanks for this
'Twas brillig, and lux-integ at 01/08/13 11:53 did gyre and gimble:
On Wednesday 31 July 2013 14:36:25 Colin Guthrie wrote:
Mount units have to be named specially after their mount points, so be
careful there e.g. if the mount point is /mnt/mymountpoint then the unit
should be called
On Thursday 01 August 2013 12:15:21 Colin Guthrie wrote:
The rootfs mount is called -.mount (i.e. a leading -)
many thanks for this
To be honest with you tho', unless you are tailoring your system for a
very specific case
yes this is so,
it is remounting / (RW) earlier in the boot process
On Thu, Aug 1, 2013 at 1:45 PM, lux-integ lux-in...@btconnect.com wrote:
On Thursday 01 August 2013 12:15:21 Colin Guthrie wrote:
The rootfs mount is called -.mount (i.e. a leading -)
many thanks for this
To be honest with you tho', unless you are tailoring your system for a
very specific
On Thursday 01 August 2013 12:58:46 Tom Gundersen wrote:
'm not following. Do you mean that systemd is already doing what you
need,
not sure as I am just learning
...but suppose
I have already mounted proc, run and sys
and I want just a read only root filesystem
--a) how do I get
'Twas brillig, and lux-integ at 01/08/13 15:25 did gyre and gimble:
On Thursday 01 August 2013 12:58:46 Tom Gundersen wrote:
'm not following. Do you mean that systemd is already doing what you
need,
not sure as I am just learning
...but suppose
I have already mounted proc, run
On Thu, Aug 1, 2013 at 4:25 PM, lux-integ lux-in...@btconnect.com wrote:
On Thursday 01 August 2013 12:58:46 Tom Gundersen wrote:
'm not following. Do you mean that systemd is already doing what you
need,
not sure as I am just learning
...but suppose
I have already mounted proc, run
On Thu, Aug 1, 2013 at 9:41 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and lux-integ at 01/08/13 15:25 did gyre and gimble:
On Thursday 01 August 2013 12:58:46 Tom Gundersen wrote:
'm not following. Do you mean that systemd is already doing what you
need,
not sure
On Tuesday 2013-07-30 02:12, Gerardo Exequiel Pozzi wrote:
In inside systemd unit, I want to avoid shell script if possible, using
units only, doing things in a systemd way. Anyway for complex tasks
where systemd does not fit, scripting seems to be necessary.
The systemd way is not {avoiding
hashmap_free() wasn't being called on m-contexts and m-fds resulting
in a leak.
To reproduce do:
while(1) {
sd_journal_open(j, SD_JOURNAL_LOCAL_ONLY);
sd_journal_close(j);
}
Memory usage will increase until OOM.
Signed-off-by: George McCollister
-u and --user-unit can be specified multiple times, so put a * in front
of it, and --user-unit can have an =, and should be looking for the
USER_UNIT not _SYSTEMD_USER_UNIT.
---
shell-completion/zsh/_journalctl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
20 matches
Mail list logo
