On 1/14/19 4:36 PM, Lennart Poettering wrote:
> On Mo, 14.01.19 10:59, Jan Synacek (jsyna...@redhat.com) wrote:
> I'd love to see some more CI hookup with Arch and Debian for example
> (right now there is zero) or even just a git preview package set or so
> that interested people can test.
Thanks for the heads up. This was unfortunately caused by two simultaneous
1) CentOS CI pool ran out of pre-installed machines
2) I forgot to handle such situation in the systemd CentOS CI code :-)
After giving the CentOS CI a few hours to get back on its tracks, I'll shortly
there's over 20 jobs to run,
it might take a good portion of the night (it's a midnight here), so please be
I'll check the status once again in the morning and try to go through any
failures (hopefully there won't be any).
On 5/28/19 10:35 PM, František Šumšal wrote
This might take a little bit longer than anticipated, as the Jenkins slave also
out of space.
On 5/28/19 10:02 PM, František Šumšal wrote:
> Thanks for the heads up. This was unfortunately caused by two simultaneous
> 1) CentOS CI pool ran ou
On 5/13/19 8:20 AM, Ulrich Windl wrote:
>> "systemd‑analyze verify" exists. Since a long long time.
> Not really: You can't verify a unit file while it's not "installed". Comare it
> to validating an XML file, for example.
That's actually not true. The argument for `systemd-analyze verify`
On 5/14/19 8:39 AM, Ulrich Windl wrote:
>>>> František Šumšal schrieb am 13.05.2019 um 17:13 in
> Nachricht <064ac942-a4d7-b547-0705-22f3262f5...@sumsal.cz>:
>> On 5/13/19 8:20 AM, Ulrich Windl wrote:
>> That's actually not true. The argument for `sys
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
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
> I agree here. While we do have `support-url` which distros can
> override, Apparently not all of them do.
On 8/28/19 9:33 AM, Ulrich Windl wrote:
> systemd in SLES 12 is causing endless frustration here:
> Yesterday I was migrating some filesystems to a new device (multipath,
> MD-RAID, LVM, filesystem, mountpoints, etc.), updating /etc/fstab and other
> files as needed.
On 8/26/19 9:43 AM, Ulrich Windl wrote:
Mantas Mikulenas schrieb am 23.08.2019 um 05:55 in
>> On Thu, Aug 22, 2019, 16:38 Ulrich Windl
>> systemd tag bot schrieb am
>>> 13:56 in Nachricht
FWIK passno > 0 in /etc/fstab configures only order in which the fsck
is performed, not the frequency. To configure the frequency as well,
I'd recommend taking a look at `man systemd-fsck@.service`, especially
the `fsck.mode=force` kernel command line parameter, which should do
I'd say calling it a 'terrible website' is somewhat subjective. I'm not a fan
of single-page websites or websites
person, who 'nominated' systemd for
having a 'terrible website' said in the thread you linked -
On 1/2/20 5:13 PM, Mike Gilbert wrote:
> On Thu, Jan 2, 2020 at 9:08 AM Lennart Poettering
>>> If possible, it would probably be wise to restrict access for pushing
>>> new branches like this.
>> Hmm, how would we do that? Any suggestion? Happy to restrict that, but
>> not sure how to
On 6/10/21 2:08 AM, Ted Toth wrote:
What do I need to do to enable log_debug logging in systemd (on
centos7), edit /etc/systemd/system.conf and set LogLevel=debug? If so,
how do I get systemd to reread the config file (kill -HUP 1)? Where do
I view the messages, journalctl -l?
If you want to
Mail list logo