UN as I know it needs to be “short lived” but not
> sure what that means in practice. That’s why I thought about splitting it
> out, with at, etc
>
> On Jul 17, 2025, at 7:40 AM, Mantas Mikulėnas wrote:
>
>
> If you need multiple instances, you could also use `systemd-ru
nd start
> our recovery program from udev rule using "at" to run outside of udev
> processing.
>
> Any other possibilities here?
>
> On Sun, Jul 13, 2025 at 10:23 PM Mantas Mikulėnas
> wrote:
> >
> > There is only ever a single instance of a unit with a sp
There is only ever a single instance of a unit with a specific name, since
the name is how you control it.
If multiple instances are needed, they need to have unique names, usually
through a template unit (foo@.service → foo@$env{something}.service).
On Mon, Jul 14, 2025, 06:07 Anthony Rossomano
Does it also move "systemd-ask-password" to -extra?
For a distro that targets embedded devices (i.e. where services aren't
going to use systemd's ask-password facility because nobody will ever be
around to manually respond to such prompts for services *anyway*), I think
it would be fine to leave o
What kind of device and how will it be used?
On Mon, Jul 7, 2025, 08:25 Zhanbang He wrote:
> It seams that udev can not share one device into multi seats? what should
> I do?
>
No, it really shouldn't detect "started by systemd" at all. These are
several independent things and you shouldn't mix them all together.
Regarding startup, systemd services have several distinct Type= settings
with different expectations and the program has no way to reliably detect
which one is
On Thu, Jun 26, 2025 at 6:27 PM Gunnar Guðvarðarson wrote:
> I have attempted to use systemd-journald as a centralized log collector,
> it works fine and the interface provided by journalctl is very convenient
> to quickly find things, following logs and other things.
>
> But I quickly discovered
nfsroot= causes the interface to be brought up very early, before udev
starts, and before it has a chance to apply its rules and .link files.
Before kernel 6.2, it was not possible to rename interfaces that were
already "up" (see linux commit bd039b5ea2a91).
On another note, even though Nam
GLib's `gdbus introspect` can show you the parameter names if they're
included in the introspection XML:
gdbus introspect -y -d org.freedesktop.systemd1 -o
/org/freedesktop/systemd1/unit/cups_2eservice
But introspection is mainly for use by language bindings (e.g. perl-dbus) –
it is not a sub
On 05/06/2025 10.00, Windl, Ulrich wrote:
Hi!
I wrote a simple service that did not start after boot. The joural
message was:
REST-server.service: Job REST-server.service/start failed with result
'dependency'.
Wouldn’t it be helpful to log WHICH dependency failed? As I started
the server
The second address looks like it comes from link-local, not from DHCP. I
suspect you have a higher-priority .network file that also enables DHCP
like yours does, but *also* sets "LinkLocalAddressing=both", like some of
systemd's built-in example .network files tend to do. Check `networkctl
status e
I don't know about journald's design performance, but at "every 40ms", I'd
probably second the suggestion to switch to something else for DEBUG-level
stuff (while perhaps keeping regular journald for regular INFO messages),
although instead of periodic-rotation-based logs consider some kind of
"rin
On Mon, Apr 14, 2025 at 7:23 PM Hadmut Danisch wrote:
> Maybe let's start at the top end:
>
>
> does systemd/networkd support wlan in ap mode?
>From what I see: Only the bare minimum; it supports creating new wlan
netdevs of 'ap' type through an .netdev file, but not switching existing
ones).
On Fri, Apr 11, 2025 at 4:14 PM Jeremy Su wrote:
> Hi,
>
> I meet a problem that systemd-resolved is not able to resolve the DNS.
>
> systemd-resolved[1237]: sd-bus: starting bus bus-api-resolve by connecting
> to /run/dbus/system_bus_socket...
> systemd-resolved[1237]: Added inotify watch for /r
On Mon, Apr 14, 2025, 18:47 Hadmut Danisch wrote:
>
> On 14.04.25 18:36, Mantas Mikulėnas wrote:
> > I don't remember seeing client-mode wlan interfaces working as bridge
> > members on regular Linux kernel. Did that change recently?
>
>
> I actually didn'
On Mon, Apr 14, 2025, 17:20 Jeremy Su wrote:
> Hi Mantas,
>
> Thank you for your reply.
>
>
> Mantas Mikulėnas 於 2025年4月14日 週一 下午5:58寫道：
> >
> > On Fri, Apr 11, 2025 at 4:14 PM Jeremy Su wrote:
> >>
> >> Hi,
> >>
> >> I m
On Mon, Apr 14, 2025, 18:35 SCOTT FIELDS wrote:
> The current docs for systemd-timedated indicates the configuration only
> supports explicit time server listings.
>
> Am I missing something in regards to support for DNS SRV records for NTP
> service?
>
> AKA:
>
> _ntp._udp.
>
It's not supported
On Mon, Apr 14, 2025, 17:03 Hadmut Danisch wrote:
> Hi,
>
> a technical question:
>
>
> I'd like to build a router on a machine with four ethernet and one wlan
> adapter, using Ubuntu 24.04 server, coming with 255.4-1ubuntu8.6. I need
> to build a bridge with two of the ethernets and the wlan a
On Sun, Apr 13, 2025, 22:35 Ian Pilcher wrote:
> I have never seen this before. After some recent update, systemctl is
> now prompting for a username when I try to start/stop/restart a unit as
> root.
>
># whoami
>root
>[root@ampersand systemd]# systemctl restart httpd
>🔐 Enter A
On Wed, Apr 9, 2025, 12:52 Windl, Ulrich wrote:
> Hi!
>
> Wasn't there an agreement that "wanting a target" is always wrong? Isn't
> "After" you are after? 😉
>
I've never heard of that kind of agreement. Want on its own isn't enough
but *something* has to Want the target for the After to have an
It sounds as if your original user is in the "video" group, so it receives
the 'group' permissions and not 'other' permissions. (They are not additive
in the POSIX model like they would be in Windows.)
Even though the device node had no specific ACL entries, it still *had* an
ACL in general, so th
On Fri, Mar 14, 2025 at 11:09 AM Fabian Greffrath
wrote:
> Am Donnerstag, dem 13.03.2025 um 10:53 +0200 schrieb Mantas Mikulėnas:
> > Does Debian support having both Pulseaudio and PipeWire installed at
> > the same time? If not, then I *think* you could list both of them in
alternatively link
~gdm/.config/systemd/user/fluidsynth.service to /dev/null, like "systemctl
--user mask" would create.)
> My guess here is that
> the "WantedBy=default.target" line should rather get replaced by
> something like "WantedBy=multi-user.target&q
On Fri, Mar 14, 2025 at 1:27 PM Fabian Greffrath
wrote:
> Am 2025-03-14 12:18, schrieb Mantas Mikulėnas:
> > Depends on whether fluidsynth ever uses the pipewire API directly (in
> > which case it should depend on pipewire.service) or whether it always
> > goes through the
s well just import /var/lib/bluetooth/*/linkkeys into the initramfs
then.
I think many BT controllers support storing link keys on the controller
itself though? Specifically for early boot (I kind of recall that being
mentioned in BitLocker context).
--
Mantas Mikulėnas
On Wed, Feb 26, 2025, 21:29 Thomas HUMMEL wrote:
> On 2/25/25 7:49 PM, Mantas Mikulėnas wrote:
>
> >> But this seems to go against the fact that intitalramfs journald can
> >> show intitialramfs systemd units (which dracut services are) logs, no ?
> >
> >
&g
On Tue, Feb 25, 2025 at 8:13 PM Thomas HUMMEL
wrote:
> On 2/25/25 6:57 AM, Mantas Mikulėnas wrote:
>
> Hello,
>
> thanks for your answer.
>
> > These seem like rsyslogd has picked them up directly from the kernel
> (from
> > the legacy /proc/kmsg guessing
sh to /var"
picks up both initramfs logs and early rootfs logs at the same time. At
least that's how it seems to work with Arch's systemd-based mkinitcpio
initramfs.
>
> 2. would then initialramfs output also be forwarded to syslog ? Only in
> debug mode ?
>
ForwardToSyslog is not retroactive. You'd need to use the pull method
(rsyslogd's imjournal module) to have it forward old messages.
--
Mantas Mikulėnas
t;
> Is there a systemd command I can run after upgrading, so the device nodes
> are created without me having to reboot?
>
> Thanks,
> Morten
>
>
>
--
Mantas Mikulėnas
"someprefix-.service.d/" feature). But of course not all services live in a
mount namespace, and not all of them *want* to live in a mount namespace...
and I don't think there is a way to define InaccessiblePaths= only for
those which already have namespacing active in some way.
--
Mantas Mikulėnas
n a service stop as well?
>
You could, but that is effectively the same as stopping the
"user-xxx.slice" similar to what you're doing now. (loginctl has
"terminate-user" and "terminate-session" subcommands which do the same.)
>
>
> Kind Regards
>
On Thu, Feb 6, 2025 at 10:29 AM Dluhosch, Michael <
michael.dluho...@airbus.com> wrote:
> Hello,
>
>
> I want a service which executes 'startFoo.sh' exactly like a user 'Foo'
> would experience it. This is my current approach:
>
> [Service]
> ExecStart=/usr/bin/startFoo.sh
>
> User=Foo
>
> PAMName
"/usr/lib/tmpfiles.d/foobar.conf".
> [/usr/lib/tmpfiles.d/foobar.conf:1] Invalid age 'mM:10d'.
>
> That looks like correct syntax, based on that online doc I found.
>
> If that is correct syntax, does that mean this feature is not
> supported by my version of syste
dification time, specify it as something
like "mM:10d" – see "Age" in tmpfiles.d(5).
--
Mantas Mikulėnas
On Wed, Jan 29, 2025 at 11:56 AM Henti Smith
wrote:
> On Tue, 28 Jan 2025 at 16:05, Mantas Mikulėnas wrote:
>
>> On Tue, Jan 28, 2025 at 4:42 PM Henti Smith
>> wrote:
>>
>>> Good day all.
>>>
>>> I'm having some timeouts on a oneshot s
each firmware update from the vendor.
>
It might very well be systemd itself doing this; on startup it bumps the
clock either to its build timestamp or to the timestamp of
"/usr/lib/clock-epoch" or "/var/lib/systemd/timesync/clock", whichever is
more recent. (The latter file is periodically touched by systemd-timesyncd.)
--
Mantas Mikulėnas
t; So the directory was not modified in the sense of a content change.
>
> I wonder: Is systemd doing “the correct thing” for PathChanged=?
>
I think that's what PathChanged= is documented to do, it reacts to all
inotify events that indicate a change, including IN_ATTRIB – not
specifically "contents".
--
Mantas Mikulėnas
On 2025-01-21 11:05, Erik Slagter wrote:
Duly noted!
But as I already wrote to Lennart, this is for a home environment.
Besides my hobby as a programmer, in daily life I am a network admin. So
I am quite aware of all the dangers lurking. There is a reason I have
quite a bunch of vlans, vrfs a
On 2025-01-21 17:00, Erik Slagter wrote:
On 21-01-2025 15:34, Cristian Rodríguez wrote:
Come on..if you do that just configure stunnel to do what you want
with PSK auth. it supports all sorts of sockets and provides you with
the minimal security you need.
I was going to say that stunnel can't
om e.g. a
D-Bus server (except with more overhead; I'd prefer JSON-RPC over SOAP, but
anything HTTP-based is definitely not light in itself).
(For my hobby projects I started with JSON-RPC over HTTPS, and ended up
with JSON-RPC inside Kerberos over raw TCP – but both were almost equally
self-contained "RPC servers", in that both kinds of requests were served
in-process and not through any 'web' stack.)
--
Mantas Mikulėnas
27;t even try connecting to it when running as a different user than root.
--
Mantas Mikulėnas
overall uses a lot of GLib2, maybe it could use
its g_network_monitor_can_reach() functions? It seems that it can either
talk to NM or directly check kernel routes for the specified server.
--
Mantas Mikulėnas
On Sat, Dec 28, 2024, 20:38 Kevin P. Fleming <
lists.systemd-de...@kevin.km6g.us> wrote:
> I've got three machines which have serial (only) consoles, all of which
> are using sd-boot from systemd 257. I use Minicom, in VT102 mode, to
> connect to these machines, and while the console generally wor
nding. Although we have taken reasonable steps to
> ensure that this email and attachments are free from any virus, we advise
> that in keeping with good computing practice the recipient should ensure
> they are actually virus free.
>
>
> On Tue, 17 Dec 2024 at 17:31, Mantas Mikulėnas
Your status output shows the unit file being in /etc; does it differ much
from the original packaged unit (if there was one)? Does `systemctl cat
asterisk` show the same contents on all systems? The most common cause of a
timeout is probably the unit and the daemon disagreeing on whether to
report
. We accept no
> legal liability for the content of the message. Any opinions or views
> presented are solely the responsibility of the author and do not
> necessarily represent those of InVADE. We cannot guarantee that this
> message has not been modified in transit, and this message should
atus=255
>
> TasksMax=infinity
>
>
>
> [Install]
>
> WantedBy=multi-user.target
>
> Should it “Wants=” or “Requisite=” network.target, too?
>
Does it make sense for a manual 'systemctl start sshd' to also start the
network? I'd say Requisite= would make sense, but Wants= a bit less so.
(I'm reminded of situations where, if you booted into single-user mode and
attempted to start udev, it would also start everything up to Xorg; it was
annoying.)
--
Mantas Mikulėnas
ev rules are rerun and apps are
> notified about the new situation via udev events)
>
I don't see logind doing that here. It seems to only set the new ACLs
directly (devnode_acl_all() in seat.c) but there are no uevents that I
could see during a VT switch.
--
Mantas Mikulėnas
7;s about it.
Normally the policies would be set up using strongSwan (via IKE).
--
Mantas Mikulėnas
ot.mount boot-efi.mount -.mount usr.mount
> var.mount tmp.mount home.mount
> Before=local-fs.target
>
> [Unit]
> Description=mytest.service
> DefaultDependencies=no
> Wants=local-fs-pre.target
> After=local-fs-pre.target boot.mount boot-efi.mount -.mount usr.mount
> var.mount tmp.mount home.mount test.mount
> Before=local-fs.target
>
>
How come your home.mount is in local-fs-pre? That is exactly the kind of
mount that would be in local-fs. In fact, why do you have *any* mounts in
local-fs-pre?
--
Mantas Mikulėnas
On Tue, Oct 29, 2024, 09:51 Henti Smith wrote:
> On Mon, 28 Oct 2024 at 19:17, Mantas Mikulėnas wrote:
>
>> On Mon, Oct 28, 2024 at 8:54 PM Henti Smith
>> wrote:
>>
>>> Where can I find detailed information on where to find the names when
>>> systemd-u
ave to do the
*opposite* – if you want systemd to react to the event of the mount showing
up, then your service has to be a dependency of the mount.
Even externally established mounts have virtual .mount units in systemd, so
if you want your service to be started by the *event* of /mnt/share being
mounted, [Install] WantedBy=mnt-share.mount would achieve that.
--
Mantas Mikulėnas
uot; or "enpX".
For example, maybe:
Property=DEVPATH=/devices/pci:00/:00:11.0/:06:00.0/net/eth*
If networkd doesn't accept wildcards, then an udev rule may work:
DEVPATH==" /devices/pci0000:00/:00:11.0/:06:00.0/net/*",
NAME="mvc-sw1"
eno2 would also have ATTRS{index}=="2" from the firmware.
--
Mantas Mikulėnas
plicated
as ENV by the stock rules to begin with – because ENV is easier to import
from multiple layers of parents.
>
> And how can I find out, which value comes with which rules so I can set
> my rules at the right time?
>
I grepped my ~/src/systemd/src for "ID_USB_INTERFACE_NUM" and saw it
defined in udev-builtin-usb_id.c, then I grepped /lib/udev/rules.d for
"usb_id". Generally safest to place your rules no earlier than 80-*, I
guess.
--
Mantas Mikulėnas
Did you place your rules in the correct order? ENV{ID_USB_INTERFACE_NUM} is
set by usb_id in 50-udev-default.rules, so it would be available in
60-foo.rules but not in 20-foo.
On Wed, Oct 9, 2024, 16:29 Daniel Spannbauer wrote:
> Hello,
>
>
> our own device (see attachement for udevadm info --at
n
> > after the systemd rule.
>
> Not sure I grok this? Why should those devices be detected as ready,
> if they don't have a file system or partition table? What's the
> rationale here?
>
> Aren't you just proprosing some workaround for your distro's broken
> udev setup? (i.e. a hosed blkid setup or so?)
>
What? Since when does readiness have anything to do with the block device's
contents in the first place?
It has always been about the device being available for use (multi-device
assembled, etc) and not about what it contains. I don't remember a single
case where e.g. /dev/sda would be "not ready" because it hasn't been
partitioned yet. Partitioning it gives readiness to *child* devices.
--
Mantas Mikulėnas
er between them in the first place;
IIRC normally none of the initramfs services are expected to survive the
transition.
--
Mantas Mikulėnas
nsient units – but
I don't know if that can be granular enough to only allow userA>userB
transitions. Most likely it will be "all or nothing", i.e. if you allow
userA to call run0/systemd-run, that user will be able to become *any*
user... A chain of predefined .service units might work better.
--
Mantas Mikulėnas
FIFOs aren't sockets – they do not have an equivalent to accept() and there
is no multiplexing of inputs; all writes to the FIFO immediately go to the
"listening" file descriptor. So it's almost more like a datagram socket
than a stream one, in a sense.
If you want a true socket that's filesystem-
to
> a wrong configuration. This can be observed in the latest systemd release
> and older versions as well.
>
> Regards,
> Matthias
>
--
Mantas Mikulėnas
I might be missing something, but... the systemd renaming is just another
udev rule, one in 80-net-setup-link, isn't it? Rules for the same interface
can't race with each other, they're processed linearly. (Rules for
*different* interfaces can race but that happens regardless of the method.)
Last
I assume you mean the inetd-style sshd@.service, not the regular
sshd.service? (Or does your distribution patch systemd-style socket
activation into sshd?)
There is usually no dependency on a shell, unless the .service unit
explicitly calls /bin/sh (note that the inetd-style socket activation uses
flags:; udp: 65494
> ;; QUESTION SECTION:
> ;_sip._tcp.osvsig-mets-prod.voip.itsvic.local. IN SRV
>
> ;; ANSWER SECTION:
> _sip._tcp.osvsig-mets-prod.voip.itsvic.local. 3600 IN SRV 20 0 5060
> osvn2-mets-prod.voip.itsvic.local.
> _sip._tcp.osvsig-mets-prod.voip.itsvic.local. 3600 IN SRV 10 0 5060
> osvn1-mets-prod.voip.itsvic.local.
>
> ;; Query time: 0 msec
> ;; SERVER: 127.0.0.53#53(127.0.0.53)
> ;; WHEN: Tue Jul 30 15:38:47 AEST 2024
> ;; MSG SIZE rcvd: 179
>
> Thanks for any help.
>
--
Mantas Mikulėnas
On Fri, Aug 2, 2024, 02:04 struth wrote:
> Hello systemd-devel group.
> I have just started using systemd-resolved to try and achieve a goal that
> I will try to explain.
> I know very little about it (web searches so far) so please excuse any
> silly questions or trains of thought.
> I have a De
Some network types use longer or shorter addresses, not all of them try to
mimic Ethernet.
For example FireWire uses 64-bit hardware addresses but IP-over-FW extends
it to 128-bit addresses in ARP for technical reasons, and I think it's the
same for Infiniband and IPoIB.
Unfortunately Networkd do
I'm not sure if that's related to homectl - it seems that you're trying to
specify User= and Group= within a user service. The whole "systemd --user"
service manager (user@xxx.service) is unprivileged and runs as your user,
so it cannot change its UID anyway or set any supplementary groups except
t
e re-enabled, and everything started
> would be re-started).
>
> But most of all if the system reboots, the timer also won’t fire any more.
>
>
>
> So can anybody explain how things should work?
>
>
>
> My expectation was that an OnUnitInactiveSec timer would fire i
processing, but I'm not sure if that works these
days.)
--
Mantas Mikulėnas
On Thu, Jul 18, 2024, 15:43 Thomas Köller wrote:
> Am 18.07.24 um 14:04 schrieb Mantas Mikulėnas:
> > Yes, but namespace persistence actually relies on filesystem access –
> > it's implemented as a bind-mount of the namespace file descriptor (onto
> > /run/netns fo
hold them.
So if you have any service options that cause a new *mount* namespace to be
created (preventing its filesystem mounts from being visible outside the
unit), then it cannot pin persistent network namespaces.
(It's also a bit overkill to use ProtectSystem for this kind of script,
really.)
--
Mantas Mikulėnas
link
>
> Am I missing something? Of course, the process running the root shell
> invoked from the command line is ultimately also a child of systemd,
> which is the system's init process.
>
--
Mantas Mikulėnas
A service could receive multiple listeners sockets, but I don't remember
systemd having an option to pass client connection sockets – and I don't
think it would make much sense, as the SMTP server is likely to close the
connection while the service is still running, and then systemd would
definitel
have missed to label the
> interface names in the .nspawn file to later reference them in the .link
> file?
>
"@if3" is not part of the name. The interface name should be just
"vb-webserver" and is based directly on the nspawn name.
--
Mantas Mikulėnas
h uses the high-level
ResolveHostname call), but I suspect that switching to the traditional
'dns' module (which makes low-level A/ queries to 127.0.0.53) would
bypass this logic.
--
Mantas Mikulėnas
v255 added a new systemd-executor binary – instead of direct
fork/setup/exec, now it's fork/exec(executor)/setup/exec(service), to avoid
doing too much stuff after fork. But the binary is executed off an open fd,
so even though you've upgraded it on disk, the manager is still holding
onto its old c
aren't working for me, although
> manually setting --background does work. Setting
> $SYSTEMD_TINT_BACKGROUND makes no difference.
>
> Any ideas?
>
--
Mantas Mikulėnas
But since it's done to a .service, it doesn't imply any Before/After (if I
remember correctly, the Wants-implies-After is .target-specific magic), so
that may be what makes RequiredBy= insufficient. Use a .conf to add both
Requires *and* After to immutable.service.
--
Mantas Mikulėnas
.
(But you can use "/bin/hostname -f" or "sysctl kernel.hostname" or "echo
testvm > /proc/sys/kernel/hostname" or pass "systemd.hostname=testvm" as a
kernel command line option to achieve the same thing.)
--
Mantas Mikulėnas
e.service, then you need
WantedBy=logrotate.service. Then each time logrotate.service is started on
schedule, it'll cause your service to be started as a dependency, and the
After= will actually work to define the order.
--
Mantas Mikulėnas
atively, run the service under the debugger: `gdb /usr/.../timesyncd`.
--
Mantas Mikulėnas
I don't know, but it might be related to this note:
https://github.com/systemd/systemd/commit/0a207d8f234ff7ea0d7988445e38685090fc930e
On Fri, Mar 29, 2024, 19:53 Nils Kattenbeck wrote:
> On Fri, Mar 29, 2024 at 7:04 AM Mantas Mikulėnas
> wrote:
> >
> > It's probab
9 (249.11-0ubuntu3.12). On my laptop (Fedora
> 40) I cannot reproduce the error and it works like in your case. The
> other two machines are servers.
>
--
Mantas Mikulėnas
On Wed, Mar 27, 2024, 16:36 Orion Poplawski wrote:
>
>
> Can I setup a unit that gets started automatically when a particular
> dev-disk-by-uuid device becomes present?
>
Just link it under dev-disk-foo.device.wants/ (systemctl enable, or
systemctl add-wants).
Alternatively, ENV{SYSTEMD_WANTS}=
, but it can continue to run
under (x)inetd or a custom `systemd-socket-activate` service (that's mainly
a CLI tool for testing but it would work as a service too).
--
Mantas Mikulėnas
On Tue, Mar 12, 2024, 15:06 wrote:
> Hi,
>
> I have a system that needs to perform some tasks on first boot. I have
> this working for the most part but I had some general questions and would
> like some guidance on the proper implementation.
>
> The tasks I need to perform on first boot include
temd startup process runs twice as many Assorted Things as my full
desktop environment did in the past, so maybe the issue is no longer
relevant.)
--
Mantas Mikulėnas
On Wed, Feb 14, 2024, 10:55 Julian Zielke wrote:
> Hi,
>
>
>
> is there a possibility to only add the routes from allowed-ips to the
> kernel routing table after the peer has connected?
>
> Because since the tunnel itself is stateless, there is no way for me to
> make use of OSPF to route packets
> I want the user sessions to start in a {mount,user} namespace. How can
> I do this? I know there is the command systemd-nspawn. But to use this
> I have to adjust the first command to start a session. Or is it
> possible by setting parameters in logind?
>
> Stef
> the Netherlands
>
--
Mantas Mikulėnas
Also, if you're using a terminal that doesn't recognize OSCs (it should
just ignore unknown ones), export SYSTEMD_URLIFY=0 to disable the hyperlink
feature that's making a mess out of systemctl output.
On Tue, Feb 13, 2024, 06:53 Sangeetha Elumalai
wrote:
> Hi,
>
> The* 'loginctl list-users'* co
You need to make sure the PAM configuration for whichever service you're
logging in through includes pam_systemd.so in the 'session' group. Check
/etc/pam.d on other distributions. (For tty logins it's /etc/pam.d/login,
but usually it's indirect via /etc/pam.d/common-session or something along
thos
.NamespaceId property t 4026531840 const
> .OnlineStateproperty s "partial"
> emits-change
> .OperationalState property s "routable"
> emits-change
> root@MK3AC-WS100269:/var/lib/evse/cache#
>
> Thanks,
> Ashok
>
>
--
Mantas Mikulėnas
On Mon, Feb 5, 2024, 14:54 Lennart Poettering
wrote:
> On So, 04.02.24 00:06, David Timber (d...@dev.snart.me) wrote:
>
> > 2: How do I get Systemd to freeze to test such program? I mean, if I kill
> > Systemd, the kernel would crash so I have to somehow tell Systemd to
> freeze?
>
> Not really,
ervice" that adds Before=foo.target. I'm not sure if
clevis integrates with that. (Although honestly I don't see much point in
using clevis for data volumes at all – just use it for the rootfs, and
regular keyfiles in /etc/private for everything else...)
--
Mantas Mikulėnas
On Sat, Jan 20, 2024 at 8:02 AM Andrei Borzenkov
wrote:
> On 19.01.2024 20:22, Mantas Mikulėnas wrote:
> > On Fri, Jan 19, 2024, 19:12 Morten Bo Johansen
> wrote:
> >
> >> On 2024-01-19 Mantas Mikulėnas wrote:
> >>
> >>> In general I'
On Fri, Jan 19, 2024, 19:12 Morten Bo Johansen wrote:
> On 2024-01-19 Mantas Mikulėnas wrote:
>
> > In general I've learned to not quite trust what the firmware shows...
> we've
> > had a batch of Skylake-or-so desktops that *did* have a CPU-integrated
> fTP
On Fri, Jan 19, 2024, 17:47 Morten Bo Johansen wrote:
> On 2024-01-18 Lennart Poettering wrote:
>
> > On Do, 18.01.24 22:53, Morten Bo Johansen (morte...@hotmail.com) wrote:
> >
> >> ~/ % systemd-creds has-tpm2
> >> partial
> >> +firmware
> >> -driver
> >> +system
> >> +subsystem
> >> +libraries
The traditional dbus-daemon keeps a separate environment for services it
spawns directly (i.e. those that don't specify SystemdService= in their
D-Bus .service files), though that it doesn't apply to services it runs via
systemd so you need to keep both in sync.
On the other hand, dbus-broker runs
Activation is not client-side, it's handled automatically by dbus-daemon –
which either spawns the service directly or starts it as a systemd service.
In this case, check whether your logs show systemd-hostnamed.service
attempting to start; either it fails to start (missing libraries?
Apparmor?) o
(or in fact you could
replace the entire user-runtime-dir@ with a simpler one that only mkdirs
and chowns), but in that case you shouldn't be saying that it's a systemd
issue that it doesn't chown something that it was never meant to chown to
begin with.
>
>
> Best regards,
Process: 16361 ExecStop=/usr/lib/systemd/systemd-user-runtime-dir
> stop 1001 (code=exited, status=0/SUCCESS)
>
>Main PID: 16329 (code=exited, status=0/SUCCESS)
>
> CPU: 48ms
>
>
>
> /etc/fstab don’t include anything on /run/user/1001 and there is no mount
&g
1 - 100 of 1058 matches
Mail list logo
