Hello all
A question about a slightly older version of systemd.
We are running systemd-37-25.fc16.x86_64.
We have a service called alarmist with a .service file like so:
[Unit]
Description=Raise alarms for %i
DefaultDependencies=no
[Service]
Type=oneshot
TimeoutSec=0
Hello all
This change, which made mount propagation default to shared:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=b3ac5f8cb98757416d8660023d6564a7c411f0a0
and which went into Fedora 17 in January 2013:
Hello all
On Sun, Apr 3, 2011 at 4:59 PM, Albert Strasheim full...@gmail.com wrote:
pam_loginuid(sshd:session): set_loginuid failed
This one is caused by:
32open(/proc/self/loginuid, O_WRONLY|O_TRUNC|O_NOFOLLOW) = 4
32write(4, 0, 1) = -1 EPERM (Operation not permitted
Hello all
I just tried to start a socket unit with ListenStream=0 in the
configuration, but this yields the following error:
Failed to issue method call: Unit zero.socket failed to load: Invalid
argument. See system logs and 'systemctl status' for details.
I would expect that it would simply
Hello all
Is there a way to specify the equivalent of RLIM_INFINITY for LimitNOFILE, etc.?
I did a quick grep of the systemd source, but couldn't find an obvious answer.
Regards
Albert
___
systemd-devel mailing list
Hello
On Mon, Apr 4, 2011 at 4:32 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 04.04.11 07:13, Albert Strasheim (full...@gmail.com) wrote:
Hello all
I just tried to start a socket unit with ListenStream=0 in the
configuration, but this yields the following error:
Failed
Hello
On Mon, Apr 4, 2011 at 8:45 AM, Albert Strasheim full...@gmail.com wrote:
I was wondering if anyone had an example of a service unit that sets
up a chroot jail with RootDirectory= but also mounts /proc, /sys and
maybe a directory with some binaries and configuration inside it?
It seems
Hello all
I'm trying to set up a configuration where a variable number of
devices under /dev/mapper get automounted.
I've started with the following:
# cat mpath\@.mount
[Unit]
Description=Data File System
[Mount]
What=/dev/mapper/%i
Where=/mnt/%i
Type=ext4
[Install]
Also=mpath@.automount
Hello
On Mon, Apr 4, 2011 at 6:01 PM, Albert Strasheim full...@gmail.com wrote:
I'm trying to set up a configuration where a variable number of
devices under /dev/mapper get automounted.
I've started with the following:
# cat mpath\@.mount
[Unit]
Description=Data File System
After reading
Hello all
I have the following socket unit:
[Unit]
Description=unix sock
[Socket]
ListenStream=@foo/%i
Backlog=128
Service=foo@%i.service
[Install]
Alias=foo@dev1.socket
Alias=sockets.target.wants/foo@dev1.socket
Alias=foo@dev2.socket
Alias=sockets.target.wants/foo@dev2.socket
Hello all
Sometimes (not sure when), when I run
systemctl stop foo.service
where foo.service is in this state:
foo.service loaded failed failed stop Foo
systemctl just hangs. I can see that it has started a process called
/bin/systemd-tty-ask-password-agent --watch
which is apparently
Hello all
I've been experimenting with
http://0pointer.de/public/systemd-units/sshd@.service
It works well, but I've noticed that each client connection adds a
line to the output in
systemctl --system --full
e.g.,
sshd@127.0.0.1:2-127.0.0.1:35006.service error failed failed
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1
([{fd=5, revents=POLLIN}])
I am running systemd-24-1.fc15.x86_64.
Full trace attached.
Regards
Albert
On Tue, Apr 5, 2011 at 10:06 AM, Albert Strasheim full...@gmail.com wrote:
Hello all
Sometimes (not sure when), when I run
Hello
Finally, a clue.
It seems after a really long time, or maybe sometimes, systemctl will print:
A dependency job failed. See system logs for details.
and sometimes (but not always), syslog will contain:
systemd[1]: Job dev-dm-0.device/start timed out.
This is caused by an
Hello again
My previous problem with an After= referring to a device seems to have
been caused by a device with a dash in the name.
I had a service called mounter@dm-0.service with
BindTo=dev-%i.device
After=dev-%i.device
which fails to find dev-dm-0.device because systemd seems to be calling
Hello
On Wed, Apr 20, 2011 at 1:49 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 12.04.11 16:15, Albert Strasheim (full...@gmail.com) wrote:
Heya,
I had the following in my syslog today while my service was running:
systemd[1]: Got invalid poll event on socket.
systemd[1
Hello
On Mon, Apr 25, 2011 at 9:59 AM, Albert Strasheim full...@gmail.com wrote:
On Wed, Apr 20, 2011 at 1:49 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 12.04.11 16:15, Albert Strasheim (full...@gmail.com) wrote:
Heya,
I had the following in my syslog today while my service
Hello
On Mon, Apr 25, 2011 at 10:03 AM, Albert Strasheim full...@gmail.com wrote:
With systemd 25 I get:
systemd[1]: Got invalid poll event on socket.
systemd[1]: foo.socket: Got invalid poll event (0x11) on socket.
I think I know what's going on here.
My service that is consuming
Hello all
OpenSSH has a chroot feature, but for it to work, the root directory
must have permissions of 0755 otherwise one gets the error:
sshd[15705]: fatal: bad ownership or modes for chroot directory component /
Is this something that systemd can control or fix when it starts? It
seems to be
Hello all
Does ConditionKernelCommandLine work in systemd-26-5.fc15.x86_64?
I've tested it with my own units and with the Fedora
fedora-autorelabel.service, but no luck.
Here's the dmesg:
[0.00] Command line: selinux=0 systemd.log_level=debug autorelabel
[0.00] Kernel command
, but the systemctl enable problem mentioned elsewhere on
this list prevented me from setting up my environment.
On Mon, Aug 15, 2011 at 1:27 PM, Albert Strasheim full...@gmail.com wrote:
Does ConditionKernelCommandLine work in systemd-26-5.fc15.x86_64?
I've tested it with my own units
Hello all
I am trying to use systemd-26 to configure a network device.
I've decided to try this instead of the standard Fedora init scripts
because I want the network configuration to depend on a kernel command
line argument (which should be possible as soon as
ConditionKernelCommandLine=foo=bar
Hello again
On Thu, Aug 18, 2011 at 10:03 PM, Albert Strasheim full...@gmail.com wrote:
I am trying to use systemd-26 to configure a network device.
I've decided to try this instead of the standard Fedora init scripts
because I want the network configuration to depend on a kernel command
Hello all
After my misadventures with SYSTEMD_ALIAS, I've tried to do it with
SYSTEMD_WANTS instead.
My udev rule:
SUBSYSTEM==net, NAME==em[1-2], TAG+=systemd,
ENV{SYSTEMD_WANTS}=foo-net-$name.service
And my foo-net-em1.service unit (just calls the existing network
scripts for now):
[Unit]
Hello
On Tue, Aug 23, 2011 at 6:09 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 21.08.11 14:01, Albert Strasheim (full...@gmail.com) wrote:
Is there a way to always get this behavior? I'd like my network
interfaces to be brought up regardless of how and when their modules
Hello
On Wed, Aug 24, 2011 at 2:04 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 24.08.11 13:26, Albert Strasheim (full...@gmail.com) wrote:
When reloading the module, there is no transaction in the debug log.
When I strace systemd, I can see that epoll returns and that systemd
Hello
On Wed, Aug 24, 2011 at 9:17 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 16.08.11 19:53, Albert Strasheim (full...@gmail.com) wrote:
Hello again
My previous example confused the issue by mentioning
fedora-autorelabal.service.
With the following in /etc/systemd/system
Hello all
I was wondering if there is some kind of guideline about whether
packaged .service files in Fedora, etc. should specify Restart=,
RestartSec=, etc.
Most of the system services shipped with Fedora are quite stable, but
it might be could to have Restarts in place for services that crash
Hello all
We started using systemd's logging today, but the documentation
tripped us up a bit and could perhaps be improved to help other users.
The example in the sd-daemon manual page makes no mention of facilities.
Thus we assumed that our logs would have the facility we configured in
---
man/systemd.xml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/man/systemd.xml b/man/systemd.xml
index a11c96e..a8a6967 100644
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -259,7 +259,7 @@
services and sockets, i.e. controls
Hello all
We have the following situation:
We have a service that is exposed through OpenSSH.
The unit looks like this:
[Unit]
Description=bar Server
[Service]
ExecStart=-@/usr/sbin/sshd bar -ddd -i -f /etc/ssh/sshd_config_bar
StandardInput=socket
StandardOutput=socket
StandardError=syslog
Hello
On Wed, Sep 7, 2011 at 7:11 PM, Albert Strasheim full...@gmail.com wrote:
Finally my question: is it possible for my custom shell to connect
stderr of bar to stdout-syslog-bridge? Is this feasible, or was
stdout-syslog-bridge designed to interact with systemd only?
Okay, wow
Hello all
I think we've found a bug in systemd-logind with systemd v35
(specifically, systemd-35-1.fc16.x86_64.rpm).
After a few thousand ssh logins, we start seeing stuff like this in
/var/log/secure:
Oct 4 13:34:29 next-10-221-0-2 sshd[568]: pam_systemd(sshd:session):
Failed to create
Hello
On Wed, Oct 5, 2011 at 1:40 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 04.10.11 15:40, Albert Strasheim (full...@gmail.com) wrote:
Hello all
I think we've found a bug in systemd-logind with systemd v35
(specifically, systemd-35-1.fc16.x86_64.rpm).
After a few thousand
Hello
On Wed, Oct 5, 2011 at 1:40 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 04.10.11 15:40, Albert Strasheim (full...@gmail.com) wrote:
Hello all
I think we've found a bug in systemd-logind with systemd v35
(specifically, systemd-35-1.fc16.x86_64.rpm).
After a few thousand
Hello all
I have the following udev rule in a machine with a bunch of disks:
SUBSYSTEM==block, KERNEL==sd*, TAG+=systemd, ACTION==add,
RUN+=/bin/systemctl restart blockinit@%k.service
The blockinit service is a one-shot service that runs a program that
checks if the block device matches some
Hello
On Thu, Oct 6, 2011 at 1:05 PM, Kay Sievers kay.siev...@vrfy.org wrote:
On Thu, Oct 6, 2011 at 11:29, Albert Strasheim full...@gmail.com wrote:
On Wed, Oct 5, 2011 at 4:10 PM, Albert Strasheim full...@gmail.com wrote:
Hello all
I have the following udev rule in a machine with a bunch
Hello all
We've had a machine up for about 9 days with lots of connections to a
socket unit:
[Socket]
ListenStream=2
Accept=yes
MaxConnections=128
[Install]
WantedBy=sockets.target
We noticed today that the socket had stopped listening. syslog said:
systemd[1]: foo.socket failed to queue
Hello
On Wed, Feb 1, 2012 at 11:24 PM, Chris Paulson-Ellis ch...@edesix.com wrote:
On 01/02/12 19:05, Lennart Poettering wrote:
(As I figured out newer Intel chipsets all have watchdogs now, so I am
actually quite keen to see this implemented in systemd now, since I can
actually test it.)
Hello
On Mon, Mar 26, 2012 at 11:44 AM, Manuel Amador rud...@rudd-o.com wrote:
memorylimit and memorysoftlimit can be determined using the ulimit system
call.
Do you mean getrlimit? man 2 ulimit on F16 says it's not implemented.
If it's getrlimit, is it RLIMIT_AS?
you cannot detect when
On Mon, Mar 26, 2012 at 4:46 PM, Lennart Poettering
lenn...@poettering.net wrote:
Also, is there some standard way for the app[M#O7lication to determine if a
MemoryLimit= is configured? We might want to automatically size some
buffers based on this limit.
You can read /proc/self/cgroup. Find
Hello all
We have a problem with machines running systemd-37-15.fc16.x86_64
hanging on reboot.
We have a system that boots from an initramfs based on F16. Nothing
much more special than yum --installroot and making a cpio archive out
of it.
We use the following kernel options that might be
Hello
On Mon, Apr 2, 2012 at 10:33 PM, Lennart Poettering
lenn...@poettering.net wrote:
What is supposed to happen next in the shutdown process? Is there any
way we can get more debugging info to find out why it is hanging?
If debug mode is enabled systemd will dump the transaction it is about
Hello all
We'd like to launch some processes in a private mount namespace so
that they can each use a limited amount of private hugepages without
running as root.
The idea was to use PrivateTmp=true to get systemd to call unshare for
us and then configure the service with:
Hello all
I'd like to find a clean way to halt a systemd system (actually, a
Docker container) when a main service stops (not just on failure).
I tried Conflicts=systemd-halt.service and calling shutdown from
ExecStopPost= but it seems both cause problems, since I end up with a
stop job for my
45 matches
Mail list logo
