On Mon, Aug 12, 2024 at 5:28 PM Gesh wrote:
> systemd.exec(5) reads:
> > In order to reference the path a credential may be read from within a
> > ExecStart= command line use "${CREDENTIALS_DIRECTORY}/mycred", e.g.
> > "ExecStart=cat ${CREDENTIALS_DIRECTORY}/mycred". In order to reference
> the
>
On Mon, Jun 17, 2024 at 10:38 AM Benjamin Drung wrote:
> On Mon, 2024-06-17 at 14:54 +0100, Luca Boccassi wrote:
> > On Mon, 17 Jun 2024 at 14:45, Benjamin Drung wrote:
> > >
> > > Hi,
> > >
> > > Ubuntu started to implement the ELF package metadata spec. It encodes
> > > the VERSION_ID from os-
On Wed, Oct 19, 2022 at 5:27 AM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> >>> Lennart Poettering schrieb am 19.10.2022 um
> 12:21
> in
> Nachricht :
>
> [...]
> > Uninstall biosdevname. It's 2022.
>
> Make Lennart happy: Uninstall everything except systemd ;-)
>
> (Sorry, I could
On Fri, Oct 14, 2022 at 7:42 PM Etienne Champetier <
champetier.etie...@gmail.com> wrote:
> Hi All,
>
> When changing distro or distro major versions, network interfaces'
> names sometimes change.
> For example on some Dell server running CentOS 7 the interface is
> named em1 and running Alma 8 it
On Fri, Sep 9, 2022 at 10:40 AM Andrea Pappacoda wr
> Il giorno ven 9 set 2022 alle 17:37:14 +02:00:00, Lennart Poettering
> ha scritto:
> > People sometimes route stuff onto the loopback device in addition to
> > the the usual 127.0.0.0/8 traffic so that it ends up on local sockets.
>
> Thanks
On Tue, Jul 30, 2019 at 3:39 PM Chris Murphy
wrote:
> On Mon, Jul 29, 2019 at 1:26 AM Lennart Poettering
> wrote:
> >
> > On So, 28.07.19 22:11, Chris Murphy (li...@colorremedies.com) wrote:
> >
> > > Using either of the following:
> > >
> > > systemd.log_level=debug systemd.journald.forward_to_
On Thu, Jul 18, 2019 at 5:02 PM Chris Murphy
wrote:
> On Thu, Jul 18, 2019 at 10:18 AM Dave Howorth
> wrote:
> >
> > On Thu, 18 Jul 2019 09:55:51 -0600
> > Chris Murphy wrote:
> > > On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala
> > > wrote:
> > > >
> > > > On Mon, 2019-07-15 at 14:32 -0600, Chri
aults would mean a regression in
functionality.
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ups. Setting
this up so that we do not get a regression in functionality compared
to old style S3 (whose policy is in firmware) falls to user space,
more specifically udev.
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Sun, Nov 5, 2017 at 9:41 AM, Rémi Pincent wrote:
> Hello,
>
> Since systemd 235, timesyncd stamp file has been moved to
> /var/lib/systemd/timesync/clock . As my /var partition is RO is created a
> symlink to a clock file located in a RW partition, I got this error :
>
> *Nov 05 16:05:44 rpi-h
ed wrong for whatever
reason the service must fail. Whether we disagree about who decide what is
a valid user name also does not matter. You cannot substitute users for
any reason.
Regards
Oliver
___
systemd-devel mailing list
systemd-d
tally fail anything that uses such a name. Falling back to
another user is not acceptable. It being root is especially bad.
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald:
>
> Am 29.06.2017 um 10:05 schrieb Oliver Neukum:
> >
> > Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> > >
> > > Well, it's a service manager. As such it keeps
.
The check systemd does adds no value. There is a reason to not start
something that is running. The reverse does not apply.
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesk
On 31/01/17, Oliver Graute wrote:
> Hello list,
>
> some further background:
>
> In my system there are different services started by systemd 225 (all
> with UMask=027). Sometimes files are created with 666 sometimes with
> 640 as I wish.
>
> ls -la
> -rw
rther background:
In my system there are different services started by systemd 225 (all
with UMask=027). Sometimes files are created with 666 sometimes with
640 as I wish.
ls -la
-rw-r- 1 oliver oliver75 Jan 11 17:30
log_20170111_163024_2.log
-rw-rw-rw- 1 oliver o
you might need is by
device class, e.g. probing HID devices, so you don't block
the keyboard.
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
t
certainly win.
>
And if we happen to look at a storage device we may see an unclean
removal if you kick the kernel off a device. I am afraid if you
really want to go to triggered probing, you need a sysctl for that.
Regards
Oliver
Hi, i have some problems with isc-dhcpd (my wifi takes too long to come
up, ath10k_pci bug, so the dhcpd times out) so i thought i will try
systemd's dhcp server as this is bound to the device.
Unfortunately i dont get it working that it provides my wifi devices
with DNS information.
My wifi de
Quota=20%
systemctl show startprocessproxy.service | grep "CPUQuota"
CPUQuotaPerSecUSec=infinity
Best regards,
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ted it stops booting with Emergency mode, even though
> > the /data is not crucial for boot
>
> RTFM - when you don't say "nofail" it's ecpected to be crucial
>
> your entry says it's crucial
That in turn raises t
On 17 February 2016 at 17:17, Lennart Poettering wrote:
> On Wed, 17.02.16 17:03, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
>
>>
>>
>> On 02/17/2016 04:51 PM, Daniel Mack wrote:
>> >Hey,
>> >
>> >[I've put all people in Cc who have had more than one commit related to
>> >systemd-bootchart
n-blkid.c fails
> resulting in an "error: /dev/sdd: No medium found" message printed to
> stderr
>
That seems to be the error. You cannot guarantee that blkid will never
see this error if the drive has removable media. It should have
to work and it is better than
duplicating ejecting and needing to keep doing
the same fixes in two places.
But that doesn't answer the basic question. What
is this policy of effectively never locking the door
doing in udev?
Regards
Oliver
On Thu, 2015-01-15 at 11:38 +0100, Martin Pitt wrote:
> Oliver Neukum [2015-01-15 11:31 +0100]:
> > No, the events are generated. And it is processed.
> > There is just no unmounting.
>
> That sounds like a bug/missing feature in cdrom_id --eject-media then.
> You could
nerate DISK_EJECT_REQUEST uevents if
> the tray is not locked. Your case sounds exactly like that?
No, the events are generated. And it is processed.
There is just no unmounting.
But what is the motivation of in effect disabling door locking?
Re
e that
unconditionally ejects media if the button is pressed? And what
is wrong with the kernel's default?
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
due to
> > udisks (using Gnome/KDE), but in the console not really.
>
> Then use udisks :)
To do what? The kernel on its own and udev on their own behave
differently. What is the correct way?
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
entative, that
> might be disastrous, because for an average user it might be close to
> impossible to deactivate power savings without working input devices.
Exactly.
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, 2014-11-07 at 12:55 +0100, Lennart Poettering wrote:
> On Fri, 07.11.14 09:23, Oliver Neukum (oneu...@suse.de) wrote:
> > It is inconsistent. That is at least partially to the inability to find
> > general rules.
>
> So what would you recommend we do?
>
> E
;
> So it does not seem to be the case that we don't currently enable
> autosuspend at all, but it's currently highly inconsistant and
> confusing.
It is inconsistent. That is at least partially to the inability to find
general rules.
Regards
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Is this possible via *.link *.network in /etc/systemd/network?
Currently I use a custom service file but using native configuration
would be much smarter.
Oliver
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
Sorry ... my fault.
Grepped for "fhandle" so do not found "FHANDLE" in README ;-)
Documentation is fine.
Best regards
Oliver
Am 24.04.2014 10:13, schrieb Oliver:
Found the solution:
lists.freedesktop.org/archives/systemd-devel/2014-February/017362.html
Maybe the de
Found the solution:
lists.freedesktop.org/archives/systemd-devel/2014-February/017362.html
Maybe the dependency of udev for CONFIG_FHANDLE in kernel should be
listed somewhere in the source tarball?
Oliver
Am 22.04.2014 18:49, schrieb Oliver:
Am 22.04.2014 07:04, schrieb Lennart
Am 22.04.2014 07:04, schrieb Lennart Poettering:
On Fri, 18.04.14 10:32, Oliver (oli...@business-security.de) wrote:
Hello.
Could anyone tell me a reason why a mount (regardless of via fstab
or "mountpoint.mount" unit file) during system boot leads to a
timeout because of device t
beginner with a systemd based system and do not know much about
the internals. What could lead to this behaviour? Is it possible that I
do anything wrong?
Please help. I'm very frustrated. If you need more Input, please tell me.
Best regards
Oliver
___
Hi all,
Just a brief announcement - I've just released Haskell bindings to
libsystemd-journal, the systemd library for writing directly to the
journal.
I've tried to be moderately type safe without giving up flexibility or
ease of use. The documentation is at:
http://hackage.haskell.org/packa
#!/bin/hi *
I'm pretty sure it's a PEBCAK but I don't get it. I do have multiple
mounts of the same device over and over after boot and I don't know why.
Please could someone help me out.
Here some specs:
root@semirhage ~ # mount | grep sd | sort
/dev/sda5 on / type ext4 (rw)
/dev/sdb1 on /h
38 matches
Mail list logo
