>>> "Pagliari, Vivenzio (Nokia - DE/Ulm)" schrieb
am
17.09.2021 um 09:52 in Nachricht
> Hello Manuel,
>
> my experience is that it is helpful for people new to systemd to "raise the
> right question" that is answered by the corresponding relationship between
> systemd units.
>
> The question
>>> Lennart Poettering schrieb am 17.09.2021 um 11:49
in
Nachricht :
> On Mi, 15.09.21 17:15, Manuel Wagesreither (man...@fastmail.fm) wrote:
>
>> Hello all,
>>
>> I'm onboarding some collegues who don't have much experience with
>> systemd. One thing I would like to focus on is the difference
>>
>>> Arjun D R schrieb am 29.09.2021 um 08:44 in
Nachricht
:
> Hi Lennart,
>
> That's a good idea but still I would like to have the prefix as it is in
> the journal . I understand it is impossible to bypass the journal and
Why not write and use your own log-output function based on vsnprintf() (
Hi!
We had a stuck networkc card on a server that seems to have caused the RAID
controller with two SSDs to be stuck on write as well.
Anyway journald dumped core with this stack:
Oct 05 20:13:25 h19 systemd-coredump[26759]: Process 3321 (systemd-journal) of
user 0 dumped core.
Oct 05 20:13:25 h
>>> Lennart Poettering schrieb am 11.10.2021 um 09:54
in
Nachricht :
> On Mi, 06.10.21 10:29, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hi!
>>
>> We had a stuck networkc card on a server that seems to have caused the RAID
> controller w
>>> Lennart Poettering schrieb am 12.10.2021 um 12:56
in
Nachricht :
> On Di, 12.10.21 12:09, Frank Steiner (fsteiner‑ma...@bio.ifi.lmu.de) wrote:
>
>> Hi,
>>
>> after upgrading from SLES 15 SP2 (systemd 2.34) to SP3 (systemd 2.46)
>> the boot messages are not only colored (which I like for seein
>>> Frank Steiner schrieb am 13.10.2021 um
>>> 18:29 in
Nachricht :
> Ulrich Windl wrote:
>
>> Stupid question: If you see bold face at the end of the serial line,
> wouldn't
>> changing the terminal type ($TERM) do?
>> Maybe construct your ow
>>> Kenneth Porter schrieb am 18.10.2021 um 21:43 in
Nachricht <95B112234248FF54AD014623@[192.168.1.16]>:
> I just installed the new‑to‑EPEL ndppd service and am seeing this in my
log:
>
> Oct 17 21:10:08 saruman systemd: Can't open PID file
> /var/run/ndppd/ndppd.pid (yet?) after start: No such
Hi!
After a change in configuration ,updates and a reboot, I saw thgis probel in
SLES12 SP5 (systemd-228-157.30.1.x86_64):
ntpd.service failed during boot. For some reason /etc/ntp.conf was missing (my
fault).
After restoring /etc/ntp.conf and trying a start, start never seems to finish
and I see
>>> Arian van Putten schrieb am 26.10.2021 um 10:41
>>> in
Nachricht
:
> Hey list,
>
> I'm reading the https://systemd.io/USER_RECORD/ spec and I have a question
>
> There are some fields in the USER_RECORD spec which are described as
> "unsigned 64 bit integer values". Specifically the field
ANother random idea: Did you experiment with tee option "--output-error=..."?
>>> Mitchel Humpherys schrieb am 27.10.2021 um 18:50
in
Nachricht
:
> On Wed, Oct 27, 2021 at 1:52 AM Colin Guthrie wrote:
>>
>> Mitchel Humpherys wrote on 26/10/2021 21:16:
>> > On my Manjaro and Ubuntu systems I'm no
>>> Chris Murphy schrieb am 03.11.2021 um 18:52 in
Nachricht
:
> There is a Discoverable Partitions Specification
> http://systemd.io/DISCOVERABLE_PARTITIONS/
>
> The problem with this for Btrfs, ZFS, and LVM is a single volume can
> represent multiple use cases via multiple volumes: subvolumes
>>> Andy Pieters schrieb am 04.11.2021 um 20:02 in
Nachricht
:
> On Thu, 4 Nov 2021 at 18:29, Michal Koutný wrote:
>
>>
>> ntp-wait.service
>> Wants=time-sync.target
>> Before=time-sync.target
>>
>>
> Ok this is not an answer, but why use ntp and not systemd-timesyncd?
Most like
>>> Uoti Urpala schrieb am 08.11.2021 um 14:47 in
Nachricht <27d2e5ff8a9b53e71bb599986060b7fbae469f1d.ca...@pp1.inet.fi>:
> On Mon, 2021-11-08 at 12:05 +0100, Sean Nyekjaer wrote:
>> Regarding,
>> https://github.com/systemd/systemd/issues/21203
>>
>> I think the point of the issue missed when th
>>> Lennart Poettering schrieb am 19.11.2021 um 10:17
in
Nachricht :
> On Do, 18.11.21 14:51, Chris Murphy (li...@colorremedies.com) wrote:
>
>> How to do swapfiles?
>
> Is this really a concept that deserves too much attention? I mean, I
> have the suspicion that half the benefit of swap space
>>> Wol schrieb am 28.11.2021 um 21:56 in Nachricht
:
> On 28/11/2021 19:56, Adrian Vovk wrote:
>> - Journal mode: is slow. It atomically writes data+hash, so the
>> situation I describe above can never happen. However, to pull this off
>> it writes the data twice. Effectively every layer of jou
>>> Martin Wilck schrieb am 01.12.2021 um 10:06 in Nachricht
:
> On Tue, 2021‑11‑30 at 14:11 +0100, Mohamed Ali Fodha wrote:
>> Thanks, but I think using setuid has a security risk for attackers,
>> so I understand there is no so much granularity to manage
>> unprivileged access to systemd in case
>>> Martin Wilck schrieb am 01.12.2021 um 10:41 in Nachricht
:
> On Wed, 2021‑12‑01 at 10:24 +0100, Ulrich Windl wrote:
>> > >
>>
>> And I wonder what's wrong with allowing the shutdown command for the
>> user in
>> sudoers.
>> (sudo $(
>>> Greg KH schrieb am 09.12.2021 um 18:24 in
Nachricht :
> On Thu, Dec 09, 2021 at 03:13:42AM +, Spencer Ku (古世瑜) wrote:
>> Hi All,
>> We are developing the redfish of openbmc, and want to expose some Ethernet
> information through the redfish interface, like packet count, drop count. My
>
>>> Chris Murphy schrieb am 10.12.2021 um 16:59 in
Nachricht
:
> On Mon, Nov 22, 2021 at 3:02 AM Ulrich Windl
> wrote:
>>
>> >>> Lennart Poettering schrieb am 19.11.2021 um
>> >>> 10:17
>> in
>> Nachricht :
>>
Hi!
I have a simple question: When will WorkingDirectory be checked? Specifically:
Will it be checked before ExecStartPre? I could not get it form the manual page.
Regards,
Ulrich Windl
Hi!
I just noticed that systemctl kill logs a (mis-named) service "{__SERVICE__}"
as "\x7b__SERVICE__\x7d.service".
Is that intended? Are braces considered bad?
(systemd-234-24.90.1.x86_64 of SLES15 SP2)
Regards,
Ulrich Windl
Hi!
debugging a problem I found out some surprising fact:
When filtering the journal with "journalctl -b
_SYSTEMD_UNIT=logrotate.service", I see an error only once, like this:
-- Logs begin at Mon 2020-11-30 11:35:08 CET, end at Mon 2021-12-27 10:19:31
CET. --
Dec 18 00:00:20 h16 logrotate[41799
>>> Lennart Poettering schrieb am 20.12.2021 um 13:27
in
Nachricht :
> On Fr, 17.12.21 08:11, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hi!
>>
>> I have a simple question: When will WorkingDirectory be checked?
>> Specifically: Will it
>>> Andrei Borzenkov schrieb am 20.12.2021 um 13:27 in
Nachricht <8581dcc7-abdc-4f35-ef41-f2ea02077...@gmail.com>:
> On 20.12.2021 15:06, Christopher Wong wrote:
>> # /etc/systemd/system/iris-detection.service
>> After=temperature-controller.service
>>
>> # /usr/lib/systemd/system/temperature-con
>>> Ludwig Nussel schrieb am 21.12.2021 um 14:57 in
Nachricht <662e1a92-beb4-e1f1-05c9-e0b38e40e...@suse.de>:
...
> The way btrfs is used in openSUSE is based on systems from ten years
> ago. A lot has changed since then. Now with the idea to have /usr on a
> separate read-only subvolume the curr
>>> Mantas Mikulenas schrieb am 27.12.2021 um 09:57 in
Nachricht
:
> On Mon, Dec 27, 2021 at 10:53 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> I just noticed that systemctl kill logs a (mis-named) service
>> "{
>>> Mantas Mikulenas schrieb am 27.12.2021 um 10:52 in
Nachricht
:
> On Mon, Dec 27, 2021 at 11:26 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> debugging a problem I found out some surprising fact:
>> When filtering
>>> Wols Lists schrieb am 27.12.2021 um 13:18 in
Nachricht <8802ee4d-230d-8013-553d-8615515ce...@youngman.org.uk>:
> On 27/12/2021 12:09, Ulrich Windl wrote:
>> Well, but why write "Failed to kill unit \x7b__SERVICE__\x7d.service" when
>> "unit {__SER
>>> Chris Murphy schrieb am 28.12.2021 um 20:02 in
Nachricht
:
> On Mon, Dec 27, 2021 at 3:40 AM Ulrich Windl
> wrote:
>>
>> >>> Ludwig Nussel schrieb am 21.12.2021 um 14:57 in
>> Nachricht <662e1a92-beb4-e1f1-05c9-e0b38e40e...@suse.de>:
>>
>>> "Manuel Wagesreither" schrieb am 10.01.2022 um 11:43 in
Nachricht <759bd805-ab37-4dc9-93cd-137668acf...@www.fastmail.com>:
> Hi all,
>
> currently, the systemd.mount man page [1] claims that "In general,
> configuring mount points through /etc/fstab is the preferred approach". Why
> is that
Hi!
When upgrading SLES15 to SP3, a newer version of systemd was installed
(246.16+suse.191.g3850086c65).
Since then I see new journal messages like these that I cannot associate with a
unit:
Jan 27 09:29:30 h16 systemd[1]: var-tmp-AP_0xC5KDJP.mount: Succeeded.
Jan 27 09:29:30 h16 systemd[22591
>>> Mantas Mikulenas schrieb am 28.01.2022 um 10:27 in
Nachricht
:
> On Fri, Jan 28, 2022 at 10:50 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> When upgrading SLES15 to SP3, a newer version of systemd was installed
>>
>>> Mantas Mikulenas schrieb am 28.01.2022 um 12:36 in
Nachricht
:
> On Fri, Jan 28, 2022, 11:59 Ulrich Windl
> wrote:
>
>> >>> Mantas Mikulenas schrieb am 28.01.2022 um 10:27 in
>> Nachricht
>> :
>> > On Fri, Jan 28, 2022 at 10:50 AM
>>> Raman Gupta schrieb am 29.01.2022 um 04:28 in
>>> Nachricht
:
>>
>> Try to set the systemd user instance's log level to 'debug'; I'm guessing
>> it's not that systemd kills processes directly but that something triggers
>> a 'systemctl stop' of the session .scope that they were in.
>
>
> H
>>> Nishant Nayan schrieb am 30.01.2022 um 04:45
>>> in
Nachricht
:
> Hi,
> Does creating a dev file in /dev creates a uevent? Does a dev file
> creation considered as a "device attached" to the machine?
I'd guess "Most likely not" as you can create /dev files without actually
having the h
>>> Thomas HUMMEL schrieb am 07.02.2022 um 18:36 in
Nachricht <3aa03772-1981-eea4-ecd2-c50b9c0d0...@pasteur.fr>:
>
> On 10/01/2022 21:50, Zbigniew Jędrzejewski-Szmek wrote:
>
>> Pretty much. There isn't any big benefit to using mount units (since the
>> fstab syntax supports all the important u
>>> Tony Rodriguez schrieb am 09.02.2022 um 02:27 in
Nachricht :
> From my understanding, it is frowned by systemd developers to
> "automatically" reload systemd via "systemctl daemon-reload" when
> /etc/fstab is modified. Guessing this is why such functionality hasn't
> already been incorpor
Hi!
I have a support case for SLES15 SP3 (systemd-246.16-7.33.1.x86_64) where
smartd is restarted for no obvious reason. Support says everything is fine, but
I disagree.
Specifically smartd.service uses:
[Service]
Type=notify
EnvironmentFile=-/var/lib/smartmontools/smartd_opts
ExecStart=/usr/sb
>>> Mantas Mikulenas schrieb am 10.02.2022 um 10:34 in
Nachricht
:
> On Thu, Feb 10, 2022 at 11:21 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> I have a support case for SLES15 SP3 (systemd-246.16-7.33.1.x86_64) where
&g
>>> Ulrich Windl schrieb am 10.02.2022 um 11:16 in Nachricht <6204E61B.426 :
161 :
60728>:
>>>> Mantas Mikulenas schrieb am 10.02.2022 um 10:34 in
> Nachricht
> :
> > On Thu, Feb 10, 2022 at 11:21 AM Ulrich Windl <
> > ulrich.wi...@rz.uni-regens
>>> Lennart Poettering schrieb am 10.02.2022 um 11:31
in
Nachricht :
> On Mi, 09.02.22 22:05, Etienne Champetier (champetier.etie...@gmail.com)
> wrote:
>
>> Hello systemd hackers,
>>
>> After flashing the firmware of some pcie card I need to power cycle
>> the server to finish the flashing proc
>>> Etienne Champetier schrieb am 10.02.2022 um
12:47 in Nachricht
:
> Le jeu. 10 févr. 2022 à 11:49, Ulrich Windl
> a écrit :
>>
>> >>> Lennart Poettering schrieb am 10.02.2022 um
11:31
>> in
>> Nachricht :
>> > On Mi, 09.02.2
>>> Mantas Mikulenas schrieb am 10.02.2022 um 14:15 in
Nachricht
:
> On Thu, Feb 10, 2022 at 3:11 PM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> >>> Etienne Champetier schrieb am
>> 10.02.2022 um
>> 12:47 in Nachricht
&g
>>> Paul Menzel schrieb am 11.02.2022 um
11:39 in Nachricht :
> Dear Adam,
>
>
> First, just a note (for myself), `ipmitool power` is a shortcut for
> `ipmitool chassis power`.
>
>
> Am 11.02.22 um 10:54 schrieb Adam Nielsen:
After flashing the firmware of some pcie card I need to power
>>> Adam Nielsen schrieb am 11.02.2022 um 12:27 in
Nachricht <20220211212751.14db2...@vorticon.teln.shikadi.net>:
>> Then these remote management cards should allow to be restarted
>> separately. The BMC I had to deal with allow that.
>
> They do under normal circumstances, but for example I ha
>>> Wol schrieb am 13.02.2022 um 01:03 in Nachricht
<129b4e49-d22d-7efb-7fc6-a44e5faa2...@youngman.org.uk>:
> More fun getting things to work ... :-)
>
> So I've got a service, scarletdme.service, which fires up my db backend
> for running interactively. However, I also need a socket service for
>>> Wols Lists schrieb am 14.02.2022 um 09:42 in
Nachricht <3320ed4b-2a0c-d7e6-a8a1-b7c83b5f4...@youngman.org.uk>:
> On 14/02/2022 08:27, Ulrich Windl wrote:
>>> And once I've got all that sorted, I'm betting I'm going to have grief
>>> gettin
>>> Michael Biebl schrieb am 14.02.2022 um 09:58 in Nachricht
:
> Am Mo., 14. Feb. 2022 um 09:42 Uhr schrieb Wols Lists
> :
>> I doubt it. Documentation is excellent at reminding you what you already
>> knew. It's piss poor at getting a newbie started.
>
> The existing documentation of systemd is
>>> Kenneth Porter schrieb am 15.02.2022 um 18:14 in
Nachricht :
> Given that interfaces can come and go, does network.target imply that
> all possible interfaces are up? Or does it just mean that the
> infrastructure is there for DHCP-capable interfaces to begin searching
> for an address?
I
>>> Stefan Schröder schrieb am 15.02.2022 um 19:05 in
Nachricht <531595111.79330.1644948301...@webmail.strato.com>:
> Situation:
>
> Many packages in a distribution ship with a default configuration that is
> not considered 'secure'.
Probably because "secure" isn't considered to be "comfortabl
>>> "Manuel Wagesreither" schrieb am 16.02.2022 um 13:28
in
Nachricht :
> Hi all,
>
> We'd like to implement a factory reset for an embedded device we are working
> on.
>
> I think the cleanest approach would be a factory‑reset.target which
> WANTS/REQUIRES reboot.target + a factory‑reset.serv
Hi!
I wonder: Is it possible with systemd to detect multiple reboots within a
specific time interval, and react, like executing some systemctl command (that
is expected to "improve" things)?
With "reboots" I'm mainly thinking of unexpected boots, not so much the
"shutdown -r" commands, but thin
>>> Stefan Schröder schrieb am 16.02.2022 um 18:11 in
Nachricht <1487454823.169440.1645031460...@webmail.strato.com>:
...
> There are reasons why the (...) decide not to ship
> with 'hardened' defaults.
...
As said before, in most cases "comfortable" and "secure" contradict.
For example: It's h
>>> Lennart Poettering schrieb am 16.02.2022 um 18:17
in
Nachricht :
> On Mi, 16.02.22 14:09, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hi!
>>
>> I wonder: Is it possible with systemd to detect multiple reboots
>> within a specific time i
>>> Lennart Poettering schrieb am 16.02.2022 um 18:59
in
Nachricht :
> On Mi, 16.02.22 12:13, Dave Howorth (syst...@howorth.org.uk) wrote:
>
>> > This could be used by applications for auditing/logging services
>> > downstream of the resolver, or to update the firewall on the system.
>>
>> Perhap
name" (where name
is one of the predefined policies).
And most of all, selecting a different policy does not make it a different
OS.
Regards,
Ulrich Windl
>
> It's 2022 ‑ nobody should be doing this by hand.
>>> Silvio Knizek schrieb am 18.02.2022 um 09:37 in
Nachricht <7d547aa30624f2dc8d22ea7f84507fa1d8e9c678.ca...@gmx.net>:
> Am Donnerstag, dem 17.02.2022 um 10:50 +0100 schrieb Ulrich Windl:
>> > > > Lennart Poettering schrieb am
>> > > > 16.
>>> Silvio Knizek schrieb am 18.02.2022 um 23:24 in
Nachricht :
> Am Freitag, dem 18.02.2022 um 09:52 +0100 schrieb Ulrich Windl:
>> > >
>> Thanks Silvio!
>>
>> That looks like I was after. But admitted: I had expected that
>> systemd could
>>
Hi!
I think there was a recent discussion saying that no unit should Want= or
Require= a target, but only use them for ordering.
I have basically three questions:
1) Is the statement above correct?
2) When is a target displayed as "started" by sysctemctl status then?
3: Which of the following
Hi!
It seems "oneshot" services are not retried when they fail.
I read systemd.service, but the manual does not explain that "oneshot" in no
candidate for RestartSec or Restart.
Is that intentional?
(systemd 228 of SLES12 SP5)
Regards,
Ulrich
>>> Mantas Mikulenas schrieb am 01.03.2022 um 16:52 in
Nachricht
:
> On Tue, Mar 1, 2022 at 4:39 PM eric.zalu...@vertiv.com <
> eric.zalu...@vertiv.com> wrote:
>
>> [ System Environment ]
>> On an embedded x86-64 Linux system, I’m running systemd v241. I have
>> Systemd-Journald logging
Hi!
In SLES15 SP3 (systemd-246.16-7.33.1.x86_64) I have this effect, wondering
whether it is a bug or a feature:
When using "journalctl -b -g raid" I see that _ome_ matches are highlighted in
red, but others aren't. For example:
Mar 01 01:37:09 h16 kernel: mega*raid*_sas :c1:00.0: BAR:0x1 B
>>> Lennart Poettering schrieb am 02.03.2022 um 17:22
in
Nachricht :
> On Mi, 02.03.22 13:02, Arian van Putten (arian.vanput...@gmail.com) wrote:
>
>> I've seen this a lot with docker/containerd. It seems as if for some
reason
>> systemd doesn't wait for their cgroups to cleaned up on shutdown.
>>> "Ulrich Windl" schrieb am 04.03.2022
um
08:07 in Nachricht <6221bac102a100048...@gwsmtp.uni-regensburg.de>:
> Hi!
>
> In SLES15 SP3 (systemd‑246.16‑7.33.1.x86_64) I have this effect, wondering
> whether it is a bug or a feature:
> When using
Hi!
In SLES15 SP3 I have found some interesting fact about systemd-coredump:
A process dumped core for strange reasons (investigated by support), and the
journal had logged:
Mar 04 07:20:02 h19 systemd-coredump[27340]: Process 27338 (sh) of user 0
dumped core.
Hi!
I wrote some services that should run when booting and some time after
booting.
As it seems the service to run during boot works, but the timer-triggered one
does not.
I have no idea why.
Here are the details:
# systemctl status prevent-fencing-loop.service
● prevent-fencing-loop.service - Pr
>>> Mantas Mikulenas schrieb am 07.03.2022 um 10:39 in
Nachricht
:
> On Mon, Mar 7, 2022 at 11:22 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> I wrote some services that should run when booting and some time after
>
>>> Lennart Poettering schrieb am 07.03.2022 um 14:08
in
Nachricht :
> On Mo, 07.03.22 12:24, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Thanks for that. The amazing things are that "systemd.analyze verify" finds
> no
>> prob
>>> Lennart Poettering schrieb am 09.03.2022 um 16:18
in
Nachricht :
> On Mo, 07.03.22 15:10, Christopher Wong (christopher.w...@axis.com) wrote:
>
>> Hi,
>>
>>
>> It seems that PrivateNetwork=yes is a memory consuming
>> directive. The kernel seems to allocate quite an amount of memory
>> for ea
Hi!
When reading the manual page systemd.unit(5), I'm not quite sure what the
difference between AssertPathExists and ConditionPathExists is:
(Condition)
If the specified absolute path name does not exist, the condition will fail.
Vs.
(Assert)
However, unlike the conditions settings, any asser
>>> Andrei Borzenkov schrieb am 17.03.2022 um 12:08 in
Nachricht
:
> On Thu, Mar 17, 2022 at 12:32 PM Ulrich Windl
> wrote:
>>
>> Hi!
>>
>> When reading the manual page systemd.unit(5), I'm not quite sure what the
> difference betw
Hi!
It's not documented, but "journalctl -g ..." seems to exit with success when
the pattern was found, and with 1 when it was not.
Can I rely on that?
The other thing is when grepping across reboots, the "-- Reboot --" is always
output, even if it does not match the pattern. Is that a bug or a
I wonder:
Why not providing some test suite instead: If the test suite succeeds, systemd
might work; if it doesn't, manual steps are needed.
My guess is that most people will quit trying once manual steps are needed.
In addition the configure procedure could include a "support window" (oldest
kern
>>> Davide Bettio schrieb am 23.03.2022 um 17:14 in
Nachricht
:
> Hello,
>
> Il giorno mer 23 mar 2022 alle ore 13:56 Lennart Poettering <
> lenn...@poettering.net> ha scritto:
>
>> > Also sadly IMAGE_VERSION doesn't allow + which is used from semver for
>> > build metadata (such as 1.0.0+21AF26
>>> Dave Howorth schrieb am 23.03.2022 um 23:34 in
Nachricht <20220323223400.569e0...@acer-suse.lan>:
> On Wed, 23 Mar 2022 22:26:15 +0100
> Michael Biebl wrote:
>> Am Mi., 23. März 2022 um 22:11 Uhr schrieb Zbigniew Jędrzejewski-Szmek
>> :
>>
>> > Or in other words: I'd prefer for such people t
>>> Greg KH schrieb am 24.03.2022 um 08:12 in
Nachricht :
> On Wed, Mar 23, 2022 at 10:34:00PM +, Dave Howorth wrote:
>> FWIW, I think Greg was a bit too outspoken calling long maintenance
>> attempts 'crazy'; that may have intimidated some. I'm thinking of
>> moving distro to one that provide
>>> Greg KH schrieb am 24.03.2022 um 14:22 in
Nachricht :
> On Thu, Mar 24, 2022 at 02:05:09PM +0100, Zbigniew Jędrzejewski-Szmek
wrote:
>> On Thu, Mar 24, 2022 at 10:28:39AM +, Luca Boccassi wrote:
>> > On Thu, 2022-03-24 at 09:38 +0100, Lennart Poettering wrote:
>> > > On Mi, 23.03.22 11:28,
Hi!
I wonder: Seeing these messages (really nothing in between) I wonder whether
such massive systemd reloading can be avoided.
Of course no program knows what the other did or does, but still these messages
look undesirable:
Apr 01 08:09:35 h19 systemd[1]: Reloading.
Apr 01 08:09:36 h19 system
>>> Lennart Poettering schrieb am 01.04.2022 um 14:18
in
Nachricht :
...
> time. Often for good reasons, quite often also for no reason but lack
> of testing. Things like that will happen. But I also think that
> Windows for example is probably better at not breaking their
> interfaces than Linux
Hi!
I have two questions for "journalctl -b -g logrotate":
1) I'm unsure what the exact rules for matching a "-g expression" are: Some
kernel messages are matched, others not.
2) When the -b restricts messages to the current boot, why is output shown like
this?:
# journalctl -b -g logrotate
--
>>> Mantas Mikulenas schrieb am 05.04.2022 um 11:08 in
Nachricht
:
> On Tue, Apr 5, 2022 at 9:36 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> I have two questions for "journalctl -b -g logrotate":
>>
>>> Luca Boccassi schrieb am 05.04.2022 um 22:07 in
Nachricht <05cf10d04274dcbff07fed88e98dca2eebb24b7d.ca...@gmail.com>:
> Hi,
>
> As part of our spring cleaning effort, we are considering when to drop
> support for split/unmerged-usr filesystem layouts.
>
> A build-time warning was added last
>>> Mike Gilbert schrieb am 06.04.2022 um 17:24 in
>>> Nachricht
:
> On Tue, Apr 5, 2022 at 4:07 PM Luca Boccassi wrote:
>>
>> Hi,
>>
>> As part of our spring cleaning effort, we are considering when to drop
>> support for split/unmerged-usr filesystem layouts.
>>
>> A build-time warning was add
>>> Wols Lists schrieb am 06.04.2022 um 21:41 in
Nachricht :
> On 06/04/2022 10:34, Luca Boccassi wrote:
>>> Symlinking /sbin or /usr/sbin binaries to /usr is also a bad concept
>>> IMHO.
>>>
>>> It seems systemd is the new Microsoft ("We know what is good for you;
>>> just accept it!");-)
>
> We
f Windows <=3 when there was no users and permissions, so they had
no concept of protection at all.
Now I think Windows is really not an example how to do things right.
Regards,
Ulrich Windl
gt;
> You guys are making your life hell, because you are afraid if making
> it difficult...
Maybe just add a manual page systemd-filesystem-concepts ;-)
Regards,
Ulrich Windl
>
> Lennart
>
> ‑‑
> Lennart Poettering, Berlin
>>> Nikhil Kshirsagar schrieb am 07.04.2022 um 13:07 in
Nachricht
:
> Hello,
>
> I gather from the discussion on
> https://github.com/systemd/systemd/issues/15141 that all numeric usernames
> would no longer be supported on servers running systemd version 245 onward.
> This was also reiterated by
>>> Wol schrieb am 08.04.2022 um 00:02 in Nachricht
:
> On 07/04/2022 17:47, Mike Gilbert wrote:
>>> So, my guess would be that the people who dislike merged-/usr are also
>>> the ones who dislike systemd, no? i.e. do they really matter if we are
>>> talking about what to support in systemd? They'
>>> Lennart Poettering schrieb am 08.04.2022 um 15:14
>>> in
Nachricht :
...
> This reminds of an RFE we have had for a while, and which I think
> would make sense to add directly to systemd: a generator that detects
> whether the battery is nearly empty at boot, and if so redirects boot
> to so
Hi!
I thin Lennart had pointed it out: If the sapplication being reloaded does not
provide any feedback when the reloading is complete, you can never be sure what
it did complete.
Adding some sleep may catch a grat number of cases whule waiting too long in
most cases.
So before discussing syst
>>> "Ulrich Windl" schrieb am 11.04.2022
um
08:26 in Nachricht <6253ca1802a100049...@gwsmtp.uni-regensburg.de>:
> Hi!
>
Sorry for the typos:
> I thin Lennart had pointed it out: If the sapplication being reloaded does
s/thin/think/
> not provide any fe
Hi!
When trying to configure forwarding of journal messages to a remote syslogd, I
realized that it seems not possible (systemd 228 of SLES12 SP5).
Is that true?
What I want is forwarding to "host:port" via UDP.
Forwarding to a local syslogd just to be able to forward to a remote syslogd
seems
>>> Lennart Poettering schrieb am 13.04.2022 um 17:38
in
Nachricht :
> On Di, 12.04.22 14:38, Elbek Mamajonov (emm.boxin...@gmail.com) wrote:
>
>> On graph I have mmcblk.device taking 1.624s. From the point that
>> this partition is where my rootfs lies, and systems does remounting
>> of rootfs,
>>> Lennart Poettering schrieb am 14.04.2022 um 09:45
in
Nachricht :
> On Do, 14.04.22 08:00, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> >>> Lennart Poettering schrieb am 13.04.2022 um
17:38
>> in
>> Nachricht :
>> >
>>> Lennart Poettering schrieb am 19.04.2022 um 11:41
in
Nachricht :
> On Di, 19.04.22 11:14, Alessio Igor Bogani (alessio.bog...@elettra.eu)
wrote:
>
>> Dear systemd developers,
>>
>> Sorry for my very bad english.
>
> Not bad at all.
>
>> We use the hostname provided by DHCP to start the righ
>>> Alessio Igor Bogani schrieb am 20.04.2022 um
>>> 22:09
in Nachricht
:
...
> The %H specifier in the commented ExecStart always returns
> "localhost". The following ExecStart is my workaround to have the
I wonder whether a future version could interpret "\%H" as "substitute %H when
it's use
>>> juice schrieb am 25.04.2022 um 17:03 in Nachricht
<4cbf03ca-7a0a-4dbe-ad00-c6f3938ff...@swagman.org>:
>
> 25. huhtikuuta 2022 16.39.56 GMT+03:00 Benjamin Berg
> kirjoitti:
>>On Mon, 2022-04-25 at 13:28 +0200, Lennart Poettering wrote:
>>>
>>> Hmm, not sure I follow? I don't know how finger
>>> "Ulrich Windl" schrieb am 26.04.2022 um
08:41 in Nachricht <6267942302a100049...@gwsmtp.uni-regensburg.de>:
>>>> juice schrieb am 25.04.2022 um 17:03 in Nachricht
...
>> Fingerprints can be used on place of username, that is OK and does not
>>> juice schrieb am 26.04.2022 um 09:11 in Nachricht
<2a780de8-efb2-749b-de43-62978958f...@swagman.org>:
> On 4/26/22 09:41, Ulrich Windl wrote:
>>>
>>> Using fingerprint for *authentication* is totally broken concept which
>>> should never be allo
1 - 100 of 545 matches
Mail list logo
