Set log size to 10M

[sirlucjan]

@arighi @htejun @Decave
As mentioned in the previous PR #88 that could help solve the log problem.

[kode54]

I see these in my journal when running these updated services:

Jan 16 18:27:20 mrgency systemd[1]: /usr/lib/systemd/system/scx_rustland.service:11: Unknown key name 'SystemMaxUse' in section 'Service', ignoring.
Jan 16 18:27:20 mrgency systemd[1]: /usr/lib/systemd/system/scx_rustland.service:12: Unknown key name 'RuntimeMaxUse' in section 'Service', ignoring.
Jan 16 18:27:26 mrgency systemd[1]: /usr/lib/systemd/system/scx_rustland.service:11: Unknown key name 'SystemMaxUse' in section 'Service', ignoring.
Jan 16 18:27:26 mrgency systemd[1]: /usr/lib/systemd/system/scx_rustland.service:12: Unknown key name 'RuntimeMaxUse' in section 'Service', ignoring.

Looks like these are restricted to specific configuration files:

https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html

[sirlucjan]

@arighi So it's just as I thought. We will have to add a journald configuration file. We need to think this through somehow

[arighi]

hm... I'm wondering, do we need to move these options inside a [Journal] section? Something like:

[Journal]
SystemMaxUse=5M
RuntimeMaxUse=5M

[sirlucjan]

Those settings that were mentioned in the previous PR are most likely assigned to the journald.conf file. It seems to me that we should not set the journal size globally.

[Byte-Lab]

@sirlucjan: Maybe Journal Namespaces could be an option? https://www.freedesktop.org/software/systemd/man/latest/systemd-journald.service.html#Journal%20Namespaces

[sirlucjan]

@Decave I've to take a look.

[sirlucjan]

@kode54 @arighi @htejun @Decave

It seems that everything works well

[htejun]

Aren't these the default?

[sirlucjan]

To be honest, I wasn't sure - I preferred to give just in case

[sirlucjan]

@htejun I've removed StandardOutput - because its default value is actually journal. StandardError has a different default value, so I haven't removed it so far.

[Byte-Lab]

The failure appears to be a double fault that's unrelated to your change or sched_ext: https://pastebin.com/FVJLm1N0.

[arighi]

FWIW, tested also on Ubuntu, everything works perfectly, thanks!