ny instances of services
having their own user accounts (httpd has its own, mariadb has its own,
sshd has its own...) Some of them even implement the "privileged listener"
model internally, e.g. httpd and sshd.
--
Mantas Mikulėnas
___
systemd-devel mail
On Wed, Mar 4, 2020 at 11:09 PM Matt Zagrabelny wrote:
> Hey Mantas,
>
> Thanks for the reply.
>
> On Wed, Mar 4, 2020 at 12:06 PM Mantas Mikulėnas
> wrote:
>
>> On Wed, Mar 4, 2020 at 7:26 PM Matt Zagrabelny
>> wrote:
>>
>>> Greetings,
&g
standard_output` as well.
>
AFAIK both stdout and stderr even get attached to the same journal pipe by
default, so they should also be interpreted in the same way.
The description of SyslogLevelPrefix= in systemd.exec(5) also says: "This
only applies to log messages writ
/etc can't be that uncommon
> and it is likely PEBKAC on our end. Is there some canonical way of
> doing overlays with Systemd and we're screwing things up?
>
If you have an initramfs, consider setting up the /etc overlay there
instead.
--
Mantas Mikulėnas
_
The default mode (Accept=no) expects your daemon to remain running forever
and handle *all* requests in the same instance. Basically once the daemon
is started and receives the listening socket, it continues working like a
traditional daemon would: start an event loop, perhaps use threads or
normally the code should
remain invisible and just make text green.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Mon, Mar 2, 2020, 16:59 Felix wrote:
> Hello everybody,
>
> I'm failing to set an alias for a link using systemd-networkd. Am I
> doing something wrong? Is this a bug?
>
>
> I'm on this systemd version:
> systemd 244 (244.3-1~bpo10+1)
> +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT
passphrases via Xterm or SSH.
X11 programs *might* be able to do that, but I have a feeling it'd be a bit
kludgy and unreliable... And either way, it would mean a passphrase entered
via X11 couldn't be used via CLI and vice versa.
--
Mantas Mikulėnas
__
is SSL connect request also be handled by systemd ?
>
No. Systemd will never read nor write the socket – your service needs to
handle SSL handshake the same way as it normally would (mostly).
(I haven't really worked with OpenSSL, but I'm guess
rch hasn't found an answer.
> What's the best way to do it please?
>
Mount --bind a persistent directory on top of /var/log/journal, using the
same method that you currently use for mounting the tmpfs.
--
Mantas Mikulėnas
___
systemd-devel mai
I don't think cron jobs are very high on systemctl's priority list.
Certainly lower than interactive use by the sysadmin. And if you actually
have to write a cron job, you can just add --quiet and be done?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
st connects to server with normal connect (server will
> do accept)
>
Your .socket specifies Accept=true, so you should remove this part as well:
the option means that systemd itself will accept the connection and only
hand your server the accepted socket.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
's a bit different from what is generally called the "boot"
partition...
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ould also avoid permission problems in case any detection methods
require root.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
. (Which IMHO was quite useful with 'auto,nofail'
combined.) This was removed in systemd v242.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ws.)
So in short I would suggest:
* Staged install: Do *nothing* except for installing the files.
* Non-staged install: Enable the service if you really need to (or create
the .wants symlink by hand), but do not start it.
--
Mantas Mikulėnas
___
syste
On Thu, Dec 26, 2019 at 9:29 PM Jeffrey Walton wrote:
> On Thu, Dec 26, 2019 at 9:35 AM Mantas Mikulėnas
> wrote:
> >
> > On Thu, Dec 26, 2019 at 2:46 PM Jeffrey Walton
> wrote:
> >>
> >> Hi Everyone,
> >>
> >> My program package inclu
a drop-in
> configuration file snippet
> '/lib/systemd/system/systemd-remount-fs.service.d/30_remount-secure.conf'
> using 'ExecStartPost=/usr/lib/security-misc/remount-secure'?
>
Honestly I think this service should not exist, and instead be a static
/etc/fstab or .mount unit configuration
nd systemd-tmpfiles-setup.service
> dependency?
>
Check /etc/tmpfiles.d and (/usr)/lib/tmpfiles.d for anything that mentions
'home'.
Run `SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create` as root and search
for mentions of 'home'.
--
Mantas Mikulėnas
__
*
automatically detect lack of EDNS support (grep the system log for
"feature"). Do the queries simply time out, or do they get rejected?
Make sure you don't have DNSSEC support set to "yes", since it depends on
EDNS.
--
Mantas Mikulėnas
___
t.
> It never does just what I want, but only what I tell it.
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
--
Mantas Mikulėnas
___
parameter as an ordering
> constraint for the network block device is also not supported for system
> root?
>
Same comment as above... how is systemd supposed to put other units before
the rootfs, if they're started *from* the rootfs?
--
Mantas Mikulėnas
_
e shutdown-initramfs.)
Either way – stopping a mount literally just unmounts the filesystem (which
is supposed to be a safe operation). I'd probably be more worried about
iscsi.service, since the blockdev losing connection *before* its fs is
unmounted is actually the dangerous part...
--
Man
On Tue, Mar 31, 2020, 22:40 Reindl Harald wrote:
>
>
> Am 31.03.20 um 20:32 schrieb Jędrzej Dudkiewicz:
> > but I understand that
> > systemd-timesyncd always uses unprivileged source port?
> what else?
>
NTP has a "Symmetric Active" mode, where both peers use port 123 as source
*and*
ts are needed.)
In practice, hostnamed does not do that (although several other systemd
daemons do). It was probably forgotten to implement.
D-Bus doesn't care about hostnames; it's just a message bus.
--
Mantas Mikulėnas
___
systemd-devel mailing l
On Mon, May 4, 2020, 23:31 Andy Pieters wrote:
> On Mon, 4 May 2020 at 15:51, Andy Pieters
> wrote:
>
>> Hi
>>
>> I'm trying to accomplish the following:
>>
>> An event happens -> I start a systemd service in response
>> after RuntimeMaxSec is reached service terminates and cleans up event
>>
and it also stops the search completely if it finds a boot ID that
it has already seen.
(What do you get from, let's say, `journalctl -o json | jq -r "._BOOT_ID" |
uniq -c`? Does it show several distinct ranges for each boot ID?)
--
Mantas Mikulėnas
__
On Tue, May 5, 2020 at 1:19 AM Andy Pieters
wrote:
>
>
> On Mon, 4 May 2020 at 23:11, Mantas Mikulėnas wrote:
>
>>
>>
>> So this is basically for implementing sudo-like caching for 2FA?
>>
>>
> Yes that's exactly it.
>
>
>> What authe
S laptop I've already had
problems after merely adding/deleting boot entries too many times, and I
*would not* want a write to happen on every single boot.
As much as I distrust the FAT implementations in my computers' firmwares, I
still trust them a little bit more than their EFI variable NVRAM
m
ame first by comparing boot
> ids. But that would still not be perfect since we could write that out
> only late (i.e. after /var becomes writable), so the order before that
> could not be reconstructed either if the system doesn't get that far.
>
Hmm, but if there's no /var in
ke Kai *has* configured it that way,
otherwise sd-encrypt wouldn't have had any effect whatsoever.
"sd-encrypt" is the mkinitcpio module (hook) which adds the standard
systemd-cryptsetup(-generator) & systemd-ask-password binaries.
systemd-gpt-auto-generator should work, as it ge
; "unlimited", why not use that string?
>
This was fixed in systemd-235 several years ago.
https://github.com/systemd/systemd/commit/21771f338d268e06dc9a10b9b08b14ff8217d4be
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
tially they provide very similar functions,
especially with linger active.
I also noticed that if the user gets lingered there is no such error
> message (which makes me think about the creation of the crond session
> through the systemd --user instance running a job)
>
Linger means the --use
On Mon, Oct 12, 2020 at 8:16 PM Thomas HUMMEL
wrote:
> Thanks for your answer. Still I'm quite confused.
>
> On 12/10/2020 18:21, Mantas Mikulėnas wrote:
>
>
> > It's a worker process which calls pam_open_session() and
> > pam_close_session() on behalf of the user@.s
o PAM not authorizing it (or due to some other
reason), this will still not prevent pam_systemd from registering the
session and creating user-.slice and making it appear in `loginctl`.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, Oct 16, 2020 at 4:13 PM Thomas HUMMEL
wrote:
>
> On 16/10/2020 13:22, Mantas Mikulėnas wrote:
>
> > But I think you're still confusing the two different kinds of "sessions"
> > that exist here. PAM open_session creates a PAM session, which
> > eventua
On Fri, Aug 28, 2020, 10:06 Ulrich Windl
wrote:
> >>> Mark Corbin schrieb am 27.08.2020 um 12:33 in
> Nachricht
> :
> > Hello
> >
> > I am working on time synchronisation issues at boot for systems without
> > an RTC (using balenaOS on a Raspberry Pi 3) and have some questions
> > about how
reload foo.service`.
Sending HUP to ExecStartPre and ExecStartPost doesn't make sense, since
those are supposed to be short-running commands – they are not allowed to
actually *have* daemons.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, Sep 25, 2020, 17:46 Francis Moreau wrote:
> Hello,
>
> I want to override /usr/lib/systemd/network/99-default.link so I need
> to create a file starting with "99-" prefix.
>
> This doesn't seem logical to me because the numbers are supposed to
> encode the priority however nothing is
s, but that should have been already covered by the existing
upstream rules:
99-systemd.rules:12:SUBSYSTEM=="tty",
KERNEL=="*tty[a-zA-Z]**|hvc*|xvc*|hvsi*|ttysclp*|sclp_line*|3270/tty[0-9]*",
TAG+="systemd"
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
doesn't properly inform systemd about the new device.
> >What does "udevadm info -a /dev/ttyPS0" output?
> I can not get a console from ttyPS0, so I can not run "udevadm info -a
> /dev/ttyPS0" in the target(xilinx pynq) board.
>
Try booting wit
link: usb0
>
> -- Information acquired via protocol DNS in 5.8ms.
> -- Data is authenticated: no
>
> Did I misconfigure something? Did I misread resolved.conf(5) which states
> “Use
> the construct "~." to use the system DNS server defined with DNS=
> preferabl
On Wed, Oct 28, 2020, 13:40 An Liu wrote:
> Hi, folks,
>
> I used to type systemctl reboot with non-privileged users, and to my
> surprise, the system goes down for the reboot.
>
> I've tested in both debian and centos 7, they act the same, however,
> systemctl halt will prompt you to enter
t;
Pull requests are usually made from your own personal repository. Use
Github's "Fork" feature to get a writable copy of the repository, then `git
remote add` its URL and push there.
For example:
git remote add fork https://github.com//systemd
git push -u fork
--
Mantas Mikulėn
That seems to be working as expected.
The initial, kernel-assigned name is always going to be an incrementing
eth#, wlan#, or something similar. It's up to the userspace (i.e. udev) to
rename it to something custom.
However, interfaces can only be renamed while they're *not* up, otherwise
the
number of processes/tasks (the default in user-.slice.d is TasksMax=33%
of...something, but it could be lowered to e.g. 10% or to 4096) without
affecting the service itself.
So I'm sure that sshd.service and user-0.slice could be tweaked somehow to
give root a higher priority at cgroup level,
t;
The kernel does not remember anything across reboots. The only way to make
a custom name persistent is to rename it from userspace every single time
(e.g. udev rules).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
will just show up as garbage on screen.
Google tells me VT421 supported sixel graphics. I'm not sure if any
programs make use of that nowadays, but if they do, then trying to use
TERM=vt421 with a terminal that doesn't do sixel will result in more
garbage on screen.
There are various other differen
claimed. If you have multiple, one of them will still be
"eth0" and will still get the IP address... you just can't be sure *which *one.
(They might even swap after a reboot.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
sical
> ext4 partition or is it required that the kernel and initrd live on the
> EFI partition too?
>
For systemd-boot, the kernel is required to be on the same EFI partition.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@
ts marked as "active (plugged)" when udev's rule processing for
that device finishes.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
I'd create a single raidcheck.service that runs daily and calls a script
that itself determines which device to check, e.g. /dev/md$[dayofyear % 16].
On Sun, Jul 26, 2020, 22:56 Ian Pilcher wrote:
> My NAS has 16 MD RAID devices. I've created a simple service
> (raidcheck@.service) that will
ith simple, other daemons wouldn't be
able to properly order After=freecusd, but with Type=notify you only need
to call sd_notify("READY=1") at the proper moment.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ow
your distro's initramfs wants to work, but at least that's what Arch does
-- since fsck is run from the initramfs, there's not much point in later
mounting it ro at all.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
I'm not sure if it's more portable. I recall FreeBSD only exposing 0–2 in
its /dev/fd by default unless you mounted a separate virtual filesystem
there. NetBSD seems to always have 64 devnodes no matter how many fds.
I don't think there's a *good* portable method (which is why closerange()
is
On Tue, Nov 24, 2020, 21:43 An Liu wrote:
> HI
>
> timedatectl set-ntp false
>
>
> what is the diff between this and
> systemctl disable ntp
>
The timedatectl command controls only systemd's own NTP client
(systemd-timesyncd.service). It doesn't care about other NTP clients such
as
On Mon, Nov 30, 2020, 23:25 Zheng, Fam wrote:
> Hi,
>
> Currently in systemd-networkd.service we have
>
> After=... systemd-udevd.service ...
>
> I know the point of it has been for tuntap as pointed out by comments
> above, but I do wonder what ensures the ordering of NIC drivers (as
> loaded
On Tue, Dec 1, 2020 at 2:31 PM Mantas Mikulėnas wrote:
> On Tue, Dec 1, 2020 at 1:46 PM Paul Menzel <
> pmenzel+systemd-de...@molgen.mpg.de> wrote:
>
>>
>> At least to me, some of the entries with timestamps from resuming should
>> have timestamps from suspend
ch
does not advance at all while the system is suspended -- so trying to
convert it to realtime will often give wrong results (the same problem as
in 'dmesg -e') unless you do something smart with combining it with
journald's __REALTIME_TIMESTAMP.
--
Mantas Mikulėnas
__
On Sat, Dec 19, 2020, 14:40 Lennart Poettering
wrote:
> On Sa, 28.11.20 01:26, Bastien Traverse (neit...@esrevart.net) wrote:
>
> > Hello everyone,
> >
> > Is it possible to specify mount options for ESP, root and LUKS devices
> when
> > using automatic partition discovery and mounting with no
t;? What do you mean by that? I am not following...
>
I suspect they mean something like ATTR{authorized}="0", which tells the
kernel to completely ignore that USB device.
(Though it's more common to set authorized_default=0 on all hubs, then
allow only trusted devi
On Sun, Dec 20, 2020 at 3:49 PM Lennart Poettering
wrote:
> On Sa, 19.12.20 15:31, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > > THere's an RFE issue open asking to support rootflags= on the kernel
> > > cmdline for the automatically discovered rootfs (that's the
ering loop:
* yourthing.service has no After=, but it runs `docker` commands and cannot
finish until docker.service is up;
* docker.service explicitly has After=network-online.target and won't start
until that target is reached;
* but network-online.target has an implicit After=yourthing.service (as
On Sun, Dec 20, 2020, 21:37 Adi Ml wrote:
> Yes. Thats exactly what I mean (what mantas said)- ATTR{authorized}="0".
> I would like to have a usb whitelist via udev and want it to be enforced on
> devices which connected pre boot too.
>
> authorized_default=0- it seems the same like
>
gt; Best regards,
> Etienne Doms
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
--
Mantas Mikulėnas
_
On Sat, Nov 14, 2020, 20:17 Mantas Mikulėnas wrote:
> On Sat, Nov 14, 2020 at 11:31 AM Nikolaus Rath wrote:
>
>> Hello,
>>
>> I just discovered that on one of my systems journald only retains log
>> entries for about 10 days:
>>
>> # journalctl | head -
(Which is still not quite
the same as 2.4 GB of *.journal files, but there's always going to be some
discrepancy due to how a binary database allocates space.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Automounts themselves are established by a magic kernel-level mount
(specifically they're "autofs" mounts), which requires root privileges.
Your systemd --user instance runs unprivileged, as your own UID, and
doesn't have the privilege to mount autofs (or anything else that isn't
FUSE).
On Tue,
the journal for logs and
> forward them on their own, without using any of the
> journal-upload/journal-remote stuff…
>
I'm less sure about the HTTP bits, but I think journal-remote can be useful
on its own, as it also takes input from stdin (doing the opposite of
It could be either, but these names are assigned by the kernel – not by
udev.
On Thu, Oct 29, 2020, 22:53 Marcin Kocur wrote:
> Hello,
>
> this is the output of turning off and on my display (using power button):
>
>
> [mk@linux ~]$ udevadm monitor
> monitor will print the received events for:
On Fri, Nov 6, 2020, 18:38 Phillip Susi wrote:
>
> Lennart Poettering writes:
>
> > What is "killprocs"?
> >
> > Is something killing services behind systemd's back? What's that
> > about?
>
> It's the thing that kills all remaining processes right before shutdown
> that we've had since the
On Fri, Nov 6, 2020, 23:31 Phillip Susi wrote:
>
> Lennart Poettering writes:
>
> > Are you running systemd? If so, please get rid of "killproc". It will
> > interfere with systemd's service management.
>
> I see.. apparently Ubuntu still has it around. How does systemd handle
> it? For
On Wed, Jan 13, 2021, 20:17 Belisko Marek wrote:
> Hi,
>
> I'm facing a strange issue. I have gsm modem and when modem is
> restarted (removed from usb bus and plugged back) one of services is
> restarted (with enabled systemd debug level):
>
> Jan 07 09:07:00 device systemd[1]: Received SIGCHLD
On Mon, Jan 25, 2021, 12:56 Badr Elmers wrote:
> Hi,
> Why nspawn is slow compared to docker podman and even qemu?!
> CPU tasks take twice of the time it takes in docker, podman or qemu
>
> here I filled a request to improve nspawn performance which contain the
> steps and the full test result:
On Tue, Jan 19, 2021, 09:50 Ulrich Windl
wrote:
> >>> Andrei Borzenkov schrieb am 19.01.2021 um 06:30
> in
> Nachricht <3a365c71-004e-031e-4153-80c376d80...@gmail.com>:
> > 19.01.2021 04:00, lejeczek пишет:
> >> hi guys.
> >>
> >> I'm fiddling with it but have run out of options/ideas.
> >>
Tatschner
wrote:
> On Wed, 2021-01-27 at 13:10 +0200, Mantas Mikulėnas wrote:
> > So it is entirely possible that when resolved makes two queries, one
> > for A records and another for , it receives conflicting
> > information about the target simultaneously being an al
perror doesn't define exit statuses. It defines syscall return codes and
libc function errno values, which usually have nothing to do with the exit
code of the whole process.
Aside from the convention that "non-zero = failure", you have to look at
the docs of the whole program (e.g. if it's a
utdown and if the goal of
After=postfix is "run my ExecStop before postfix gets stopped", then
ability to queue doesn't help all that much.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
If you only care about processes on the same system – why not put the
actual socket in /run, as an AF_UNIX socket? That's mostly what /run is for.
On Tue, Jun 15, 2021, 04:18 John Ioannidis wrote:
> I have an instanced service that gets started and stopped by another
> service: *alice.service
".
>
> Add:
> One or more of the associated service files
> StandardInput/StandardOutput/StandardError options should be set to
> socket for this option to work.
>
IMHO that is a bit odd. I don't really see the reason why the option
wouldn't work with any Accept
dumpctl is fine with missing/removed coredump files --
that's part of the normal operation; actual dumps are cleaned out much
faster than the corresponding journal entries. You'll probably already see
some of them marked "missing" in the list.
--
Mantas Mikulėnas
ative). So if there are no
objections I'll make a PR to update systemd's README files to "s/
freenode.org/libera.chat/g" sometime later.
--
Mantas Mikulėnas (grawity)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.
ttps://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, Jun 2, 2021, 08:04 Greg KH wrote:
> On Tue, Jun 01, 2021 at 09:38:37PM +0200, Michael Biebl wrote:
> > Am Di., 1. Juni 2021 um 20:44 Uhr schrieb Greg KH <
> gre...@linuxfoundation.org>:
> > > Works for me! Make sure you are not trying to connect to 'https'.
> >
> > No https? Why?
>
>
/var/run/log ramfs...
>
That's already the default if /var/log doesn't exist. To ensure /run is
always used, you should set "Storage=volatile" in journald.conf.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.or
: Failed to set DUID-EN: No medium found
> eth0: DHCP6 CLIENT: Failed to set DUID: No medium found
>
My guess is that it's related to /etc/machine-id somehow becoming
inaccessible, since networkd's DUID-EN (DUIDType=vendor) is based on that.
--
Mantas Mikulėnas
_
ngs which use the machine-id anyway...
> Thanks
>
> --
> Alessandro Tagliapietra
>
>
> On Tue, Jun 1, 2021 at 12:13 AM Mantas Mikulėnas
> wrote:
>
>> On Tue, Jun 1, 2021 at 10:07 AM Alessandro Tagliapietra <
>> tagliapietra.alessan...@gmail.com> wrote:
>&
; drwxr-xr-x 87 root root 0 Jul 2 15:05 system.slice
> drwxr-xr-x 7 root root 0 Jun 30 15:22 user.slice
> ubuntu@vrni-platform:/tmp/debraj$ sudo umount /tmp/tuk
>
> Can someone suggest what configuration I am missing?
>
>
> ___
> systemd-devel mailing
"Warning: myfancyservice.service changed on disk. Run 'systemctl
> daemon-reload' to reload units."
>
systemd can't make non-systemd tools (such as `mount`) display warnings.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
in/sync` from shell, since it does
exactly the same thing. In general there should be nothing special about
systemd calling sync(), it's purely a kernel problem. The only difference
that I can think of is that systemd begins the sync() while all services
are shutt
On Sat, Jun 26, 2021, 14:06 Johannes Köhler
wrote:
> Hi systemd maintainer, again!
>
> with my last post i got a hint to
> follow the netiquette. My netiquette
> with now, was: read manpages and html
> searches before asking stupid questions... :)
>
> So to say, i am happy about private messages
in the
network? (If it's to check that the physical interface is working, then
just the fact that you somehow acquired a lease would be enough. no?)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Sun, Jan 24, 2021, 20:58 Weatherby,Gerard wrote:
> When systemd-automount queries an NFS server with multiple IPs, does it
> try all of the them (the default behavior of the similar autofs package) or
> just use one, or something else?
>
Systemd does not have any special handling for NFS –
afterwards. Currently it has recorded 1.988s total CPU usage
after 12 days of uptime.
> So the punchline is, that timesynd is not really usable with ipv6
> networks? Am I getting that correct?
>
No, sounds more like it's just not really usable with *your* IPv6
s like it would make it
*less* useful with two sessions, because you would have no way to run a
second instance for the other session anyway.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Thu, Mar 11, 2021, 13:17 Ulrich Windl
wrote:
> Hi!
>
> I have a unit that uses logger, and I want to run it after syslog is
> available. So I added syslog.socket as dependency, but it fails:
> Mar 11 12:11:02 jeos1 systemd[1]: syslog.socket: Socket service
> syslog.service not loaded,
0/0 because I don't know the "wanted" destinations in
advance, but at the same time I don't want the system to *default* to
sending all my traffic halfway around the world and back, so it has to be
"on demand".
People are in a hurry to suggest "openvpn is meh, use wg-quick" a
I would suggest adding StandardError=journal, so that you get to see the
Python exceptions when they happen.
On Mon, Mar 22, 2021, 04:21 Matt Zagrabelny wrote:
> Greetings,
>
> I'm running systemd 241-7~deb10u6, Debian 10 (Buster).
>
> I am attempting to have an inetd like service run, where
Normally I think systemd expects the kernel to do this on its own.
On Mon, Mar 1, 2021, 12:31 Belisko Marek wrote:
> Hi,
>
> I have a case when a board boots without network connection but RTC
> have the correct date/time. Does systemd use RTC date/time to set
> systemd time or it needs to be
801 - 900 of 1112 matches
Mail list logo
