On 8/11/20 2:27 PM, Lennart Poettering wrote:
Can you run systemctl with SYSTEMD_LOG_LEVEL debug? Anything
interesting in the debug output it generates then? I wonder where the
I/O error comes from...
Sure:
# export SYSTEMD_LOG_LEVEL=debug
# systemctl kill -s HUP rsyslog.service
Bus n/a: cha
I've made a mistake and have executed a forkbomb-like task. Almost
immediately, the system became unresponsive, ssh session froze or were
very slow to output even single characters; some ssh sessions timed out
and were disconnected.
It was not possible to connect a new ssh session to interrupt
Just FYI and for the sake of cross referencing, the inhibition logic was
mentioned on the list today in a thread: "systemd-inhibit don't work".
A developer says he will work on the patch for this RFE shortly.
Col
Zheng SHAO wrote on 04/08/2020 13:39:
> Hello,
>
> First thanks for your advise.
>
Am 10.08.20 um 15:37 schrieb Lennart Poettering:
> On Mo, 10.08.20 15:05, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>> well, i would expect that the reboot in the scond ssh-session is
>> refused...
>>
>> [root@master:~]$ /usr/bin/systemd-inhibit --what=shutdown --who=root
>> --why="Ba
On Wed, Aug 5, 2020 at 4:12 PM Thomas HUMMEL
wrote:
>
>
> What I understand here in my case is that NAME is not empty (because of
> biosdevname step) so I don't understand why I don't end up with em1
> instead of the
> onboard style name. This would mean ID_NET_NAME has been set in a
> previous
On Di, 11.08.20 14:14, Harald Dunkel (harald.dun...@aixigo.com) wrote:
> Hi folks,
>
> sending a HUP to rsyslog using the "systemd way" gives me an error:
>
> # systemctl kill -s HUP rsyslog.service
> Failed to kill unit rsyslog.service: Input/output error
>
> rsyslog receives the sign
Hi folks,
sending a HUP to rsyslog using the "systemd way" gives me an error:
# systemctl kill -s HUP rsyslog.service
Failed to kill unit rsyslog.service: Input/output error
rsyslog receives the signal, but the exit value of systemctl indicates
an error, affecting the logrotate
