Why can't you use After= ?
On 7/12/24 12:42, t.schnei...@disroot.org wrote:
Hello,
I have a backup job (using rsnapshot) that must be executed daily,
weekly and monthly.
Therefore I created these systemd-timers:
|# /etc/systemd/system/rsnapshot-daily.timer [Unit]
Description=rsnapshot daily
I can't tell more about the IPoIB going down after networkd restart
without additional debugging info. But from the complains, did you try
removing the problematic keys (ipoib is part of netdev, not network.
network has no knowledge of the device type)?
Also are you sure
80:00:02:08:fe:80:00:
I have an use case that requires persisting a mount (/sysroot/mnt) from
initramfs. The system is booted with systemd.volatile, so only /usr of
/sysroot is used, rest is tmpfs.
Ideally I should add the mount unit in the /usr itself but /usr is a
read only signed fs that I can't modify for reaso
du -sh /usr/lib/systemd/
13M /usr/lib/systemd/
du -sh /usr/lib64/systemd
6.4M /usr/lib64/systemd
i.e. about 20M with most stuffs of systemd package installed. Is it too
large for initrd? Idk about your setup, might be embedded flash..
On 9/23/24 12:03, dharm...@microchip.com wrote:
Hi
ramfs. This will give a very small amount of time advantage
of launching systemd in rootfs and running basic.target. Not sure if
that is what you are looking for.
On 9/25/24 06:07, dharm...@microchip.com wrote:
Hi Serenissi,
On 24/09/24 2:58 pm, serenissi wrote:
du -sh /usr/lib/systemd/
man systemd.exec:
PrivateMounts=
Takes a boolean parameter.
When turned on, this executes three operations for each invoked
process: a new CLONE_NEWNS namespace is created, after which all
existing mounts are remounted to MS_SLAVE to disable propagation
from the unit's processes
What is the usecase for this? sysexts are extensions to /usr (and /opt).
Services don't write to /usr usually (extensions are usually read only
too). Anything being read is opened as a fd which survives the
unmount-mount operation. I can't think of any reason a service would
want to "lock" /usr
I noticed a phenomenon about logind managed devices (drm node). I have
two users, localuser and testuser, the former has a session in seat0
(this is important). I attached drm card1 to new seat `seat1` and set
777 permission to the dev node /dev/dri/card1. Now the acl looks like
# file: dev/dr
::-" entry was left unchanged with
no permissions. If you're not owner but are in the 'video' group you
therefore get no access.
Use "setfacl -m g::rwx" to change the main group access entry instead.
On Tue, Apr 1, 2025, 17:29 serenissi wrote:
I noticed a pheno
This is about fs UUID, not GPT PARTUUID. vfat filesystems do not support
standard UUID format for historical reason.
On 4/2/25 14:32, Karel Zak wrote:
On Tue, Mar 25, 2025 at 09:00:09PM -0600, Thayne Harbaugh wrote:
Response in-line:
On Tue, 2025-03-25 at 16:53 -0600, Thayne Harbaugh wrote:
It seems very strange. systemd-nspawn should have nothing to do with
whether it is running in vm or what is the host of the vm. Try to see
what systemd-detect-virt see's in each case anyway.
For debugging, you can enter the nspawn container --boot and see if
cgroup fs is mounted the same in al
11 matches
Mail list logo
