Version: systemd-242-2.2.x86_64, dnsmasq-2.80-4.1.x86_64,
bind-9.11.2-44.3.x86_64, avahi-0.7-7.3.x86_64 from OpenSuSE Tumbleweed.
Here's my use case: There's a master directory server, two slaves, and a
bunch of leaf nodes. All support IPv4 and IPv6. All the Linux boxes
run systemd and systemd-
Thank you for the response! I don't think I did a great job asking an actual
question in my last email, so let me clarify.
What I am currently trying to understand is what the differences between how
and when the different timestamps for each service are logged. The confusion
comes from the fa
Am 03.07.19 um 11:59 schrieb Ulrich Windl:
> Well an actual fact: I upgraded a system yesterday, and I spend about eight
> reboots and about 5 hours just to find out WHY systemd booted into an
> emergency
> shell. Compared to the old init I would have found and fixed that in one boot
> I
> gues
Am 03.07.19 um 11:53 schrieb Ulrich Windl:
> I agree that the major problem with systemd was that distributions switched 3
> or 5 years too early to it.
guess where you would be now without them solving most fo the problems
over the past years for people coming like you late to the party
guess
Am 03.07.19 um 08:37 schrieb Ulrich Windl:
> The really annoying thing with systemd is that if SOMETHING fails during boot,
> the complete boot is aborted and you are put into an emergency shell.
this is not true
there are very rare cases where you end in the emergency shell
> with the fact th
On Mi, 03.07.19 08:37, Ulrich Windl ([email protected]) wrote:
> >> I agree here. While we do have `support-url` which distros can
> >> override, Apparently not all of them do.
> >> We could probably change our build system, that `support-url` needs to
> >> be set explicitly and if
On Di, 02.07.19 12:30, Jay Burger ([email protected]) wrote:
> Hi,
>
> I am curious if there is a way to single step through the systemd startup
> of services?
So this exists, in theory in systemd.confirm_spawn= on the kernel
cmdline. But it's not without pitfalls. In particular, some dis
On Mi, 03.07.19 11:59, Ulrich Windl ([email protected]) wrote:
> > Thank you for understanding,
>
> OK, I'll write a positive message about systemd: "Great, it made me spend
> several hours to find and fix boot problems, where without systemd I would had
> just idle time. A great i
Ubuntu 18.04, HWE kernel 4.18.0-25-generic, systemd 237-3ubuntu10.23
I have created a nspawn container with a minimal Ubuntu and booted the container
without any problems. There were no problems and I used the default settings.
Now I see some strange permission errors which I can't explain:
Insi
>>> Lennart Poettering schrieb am 03.07.2019 um 11:01
in
Nachricht <20190703090130.GB12011@gardel-login>:
> On Mi, 03.07.19 08:42, Ulrich Windl ([email protected]‑regensburg.de)
wrote:
>
>> >>> Jay Burger schrieb am 02.07.2019 um 19:30
in
>> Nachricht :
>> > Hi,
>> >
>> > I am curious if there
>>> František Šumšal schrieb am 03.07.2019 um 11:01 in
Nachricht :
[...]
> Honestly, I'm kind of impressed you stamp the "bad bad systemd" phrase all
> over
> the place several times in your emails, yet you still expect people to be
> able
> to (willingly) help you.
I may have an opinion, just
On Mo, 01.07.19 17:03, [email protected] ([email protected]) wrote:
> On Mon, 01 Jul 2019 08:20:23 +0200
> "Ulrich Windl" wrote:
> > >>> Simon McVittie schrieb am 11.06.2019 um
> > >>> 16:29 in Nachricht
> > <20190611142939.GA6676@horizon>:
> > > On Tue, 11 Jun 2019 at 15:44:07 +0200,
On Mi, 26.06.19 16:30, Sam Gilson ([email protected]) wrote:
> Hey everyone, I've got a quick question about how the timestamps
> that are gathered by systemctl are emitted by systemd. My
> organization has a service that runs fairly early in boot (timestamp
> X ), it has DHCP to an internal
On Di, 02.07.19 18:51, František Šumšal ([email protected]) wrote:
>
>
> On 7/2/19 4:36 PM, Michael Biebl wrote:
> > Am Di., 2. Juli 2019 um 16:16 Uhr schrieb Paul Menzel
> > :
> >> Reading the output above, I can see, why the people contact this mailing
> >> list.
> >
> > I agree here. While we
On Mi, 03.07.19 08:42, Ulrich Windl ([email protected]) wrote:
> >>> Jay Burger schrieb am 02.07.2019 um 19:30 in
> Nachricht :
> > Hi,
> >
> > I am curious if there is a way to single step through the systemd startup
> > of services? I don't find any such feature and am curious w
On 7/3/19 8:37 AM, Ulrich Windl wrote:
František Šumšal schrieb am 02.07.2019 um 18:51 in
> Nachricht :
>
>>
>> On 7/2/19 4:36 PM, Michael Biebl wrote:
>>> Am Di., 2. Juli 2019 um 16:16 Uhr schrieb Paul Menzel
>>> :
Reading the output above, I can see, why the people contact this mailin
On Mi, 03.07.19 09:07, Ulrich Windl ([email protected]) wrote:
> Hi!
>
> I'm having a problem created by systemd: A temporary directory is to
> be created that is owned by a user found in LDAP. However as all
> temporary directories are created way before networking is
> available
Hi!
I'm having a problem created by systemd: A temporary directory is to be created
that is owned by a user found in LDAP.
However as all temporary directories are created way before networking is
available, I cannot user the user name, nor can systemd delay creating that
directory after networ
18 matches
Mail list logo
