Units like "systemd-resolved.service" contain with good reason:
"ProtectSystem=strict"
This of course bind mounts mounted filesystems into the units userspace.
"strict" is
"If set to "strict" the entire file system hierarchy is mounted
read-only, except for the API file system subtrees /de
On 31/10/2024 12:48, Lennart Poettering wrote:
On Do, 31.10.24 10:20, Steve Traylen (steve.tray...@cern.ch) wrote:
Hi,
I was trying to suppress user scope units that are considered failed due to
them requiring a SIGKILL. Typical log might be.
Oct 30 10:27:55 node989.example.ch systemd[1
Hi,
I was trying to suppress user scope units that are considered failed due
to them requiring a SIGKILL. Typical log might be.
Oct 30 10:27:55 node989.example.ch systemd[1]: session-3804.scope:
Killing process 1550946 (node) with signal SIGKILL.
Oct 30 10:29:25 node989.example.ch systemd[1
Example with lingering **disabled**
root> systemd-run --service-type=exec --user --machine eric@.host
/usr/bin/sleep 1m
With this
The systemd --user instance is started for Eric and also the sleep is
started.
However after < 10 seconds or so the transient unit and user service is
a
nd
[Service]
ExecStart=/usr/bin/ls /etc/passwd /etc/notexisting
StandardOutput=file:/run/emailoutput.socket
StandardError=file:/run/emailoutput.socket
A single email of Output and Error is generated - that's great - thanks.
No more questions.
Steve.
On Thu, Sep 5, 2024, 13:38 Steve Tra
Was trying to set up a trivial socket and service to process multiple
inputs:
# Socket emailoutput.socket
[Unit]
Description=Send email via a socket.
[Socket]
Accept=yes
ListenFIFO=/run/emailoutput.socket
# Service emailoutput@.service
[Unit]
Description=email
[Service]
ExecStart=/usr/bin/mai
Hi,
I have a old legacy service that's a bit odd in that it was previously launched
by xinetd but is weird in that:
After an initial quite quick auth and set up a daemon is forked of to run the
much longer process.
Setting this up with a socket me.socket and me@.service does not work quite
rig
On 01/02/2024 14:48, Steve Traylen wrote:
On 01/02/2024 13:45, Andrei Borzenkov wrote:
On Thu, Feb 1, 2024 at 3:25 PM Steve Traylen
wrote:
Hi,
I'm trying to understand why I am only retaining just a couple of days
of logs when I would like to have more.
The system journalctl head o
On 01/02/2024 13:45, Andrei Borzenkov wrote:
On Thu, Feb 1, 2024 at 3:25 PM Steve Traylen wrote:
Hi,
I'm trying to understand why I am only retaining just a couple of days
of logs when I would like to have more.
The system journalctl head of the logs is only today:
Feb 01 10:
Hi,
I'm trying to understand why I am only retaining just a couple of days
of logs when I would like to have more.
The system journalctl head of the logs is only today:
Feb 01 10:47:14 nodeX.example.ch systemd-journald[722]: Data hash table
of /var/log/journal/c33ef6d0ada04ec4abc79c567a7d94b
naware of.
Any suggestion as to what to do here.
Steve.
--
Steve Traylen
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
oxy-server
[Install]
WantedBy=multi-user.target
--
Steve Traylen
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
12 matches
Mail list logo
