On Fri, Jul 24, 2015 at 09:24:31PM +, Mike Gabriel wrote:
> On Fr 24 Jul 2015 21:52:21 CEST, Petter Reinholdtsen wrote:
> >
> >killer depend on updated utmp/wtmp information (check last/w/who). If
> >the active SSH sessions did not register their login with utmp, killer
> >can not know their
[Wolfgang Schweer]
> As an alternative, I'm just wondering if the killer job could be taken
> over by systemd-logind, see 'man logind.conf'. This would allow to keep
> processes of stated users and other actions, too.
>
> Also, at least with systemd version 226, it would be possible to drop
>
I have to remove killer fromm all ws.
Otherwise users get logged out every 30 min
Regards
Giorgio
Il ven ott 9 13:44:15 2015 GMT+0200, Petter Reinholdtsen scrive:
> [Wolfgang Schweer]
> > As an alternative, I'm just wondering if the killer job could be taken
> > over by systemd-logind, see
Hi Petter,
On Fr 24 Jul 2015 21:52:21 CEST, Petter Reinholdtsen wrote:
[Mike Gabriel]
Today I saw killer kill sshd user processes (i.e., active SSH
sessions).
killer depend on updated utmp/wtmp information (check last/w/who). If
the active SSH sessions did not register their login with
[Mike Gabriel]
Today I saw killer kill sshd user processes (i.e., active SSH
sessions).
killer depend on updated utmp/wtmp information (check last/w/who). If
the active SSH sessions did not register their login with utmp, killer
can not know their processes belong to active login sessions.
--
Package: killer
Version: 0.90-12
Severity: important
Today I saw killer kill sshd user processes (i.e., active SSH sessions).
This should not happen. It happened on a Debian Edu jessie main server (after
(dist-)upgrade from squeeze).
I will investigate further and provide more info while
6 matches
Mail list logo
