This bug was initially created as a copy of Bug #2156780

I am copying this bug because: 
It applies to RHEL-9 too.


Description of problem:

I have configured the new systemd feature StopIdleSessionSec. And seems to be working because I can see sessions being stopped. Sadly without any evidence why the user session is stopped.

Looking at https://github.com/redhat-plumbers/systemd-rhel8/commit/24439b08e3a3437b423553c385cde1d4cddf18f6#diff-0b375f3118a9ae0b86c5bd218491126a329817a5bfeb41fff8f164b36b00604cR676 the info that a session is idle is logged only on debug level instead of info level that to inform the administrator what is going on.

Can we please adjust the log severity of the idle message to an info level  so it is included in journal/syslog so that it is for administrators traceable why sessions are stopped?


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Modify /etc/systemd/logind.conf, add 'StopIdleSessionSec=10'
2. sudo systemctl restart systemd-logind
3. Run 'while true; do echo $n; sleep 1; n=$(( n + 1 )); done'
4. Login again
5. Run 'sudo grep -i idle /var/log/messages /var/log/secure'

Actual Result:
- Session correct killed at 10 seconds
- After login again the grep does not give any result (for 'idle' keyword)

Expected results:

Below line logs about idle session, but its only in debug mode, can we get this for info (default) log severity?

log_debug("Session \"%s\" of user \"%s\" is idle, stopping.", s->id, s->user->name);


Additional info: