This is a bad idea because I use tmux to manage my shell. If there is an autokiller, then I'll have to reopen and get my panes how I like them again. I may not be working in a pane or I may be running something like tail to read log files, or something else, so an inactivity killer would kill all of that. tom29739, Tool Labs user.
>>* and a shell should automatically terminate on labs, *>>* if it's been inactive for 30 mintues. *> > No. I use mosh to connect to Labs. depening on circumstances such as > commuting, pause times, and others, the inactiity time may well exceed > half an hour. > > Make it unlimited. > > Purodha > > >> On 04.04.2016 21:54, Maximilian Doerr wrote: >>* I think the primary problem is that users keep running bot scripts on *>>* it, when they shouldn't, and I think the easy solution would be to *>>* implement a killer, which kills all scripts started on tools-login *>>* when the user logs off, or if it has been running for more than 15 *>>* minutes. It's okay to run it on -login quickly to understand how it *>>* will interact with the labs environment, but it's not supposed to be *>>* permanent. Another seemingly recurring problem, and I'm guilty of it *>>* too is when users pointlessly leave shell sessions open. That's *>>* also *>>* a security risk, and a shell should automatically terminate on labs, *>>* if it's been inactive for 30 mintues. *>>>>* Just my thoughts. *>>>>* Cyberpower678 *>>* English Wikipedia Account Creation Team *>>* Mailing List Moderator *>>* Global User Renamer *>>>>* -----Original Message----- *>>* From: Labs-l [mailto:labs-l-bounces at lists.wikimedia.org <https://lists.wikimedia.org/mailman/listinfo/labs-l>] On Behalf Of *>>* Yuvi Panda *>>* Sent: Monday, April 04, 2016 3:43 PM *>>* To: Wikimedia Labs <labs-l at lists.wikimedia.org <https://lists.wikimedia.org/mailman/listinfo/labs-l>> *>>* Subject: [Labs-l] [Tools] New bastion at tools-login.wmflabs.org <http://tools-login.wmflabs.org> *>>>>* Hello! *>>>>* I've moved tools-login.wmflabs.org <http://tools-login.wmflabs.org> to a new bastion host with twice *>>* the RAM and CPU of the old one. This should hopefully provide a *>>* better *>>* bandaid against it getting overloaded up. More discussion about a *>>* longer term solution at https://phabricator.wikimedia.org/T131541 <https://phabricator.wikimedia.org/T131541> *>>>>* You can find new fingerprints at *>> >>* https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/tools-login.wmflabs.org <https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/tools-login.wmflabs.org> *>>>>* Apologies for the interruption! I'll leave the old bastion up at *>>* tools-bastion-05.eqiad.wmflabs. *>>>>* -- *>>* Yuvi Panda T *>>* http://yuvi.in/blog <http://yuvi.in/blog> *>>>>* _______________________________________________ *>>* Labs-l mailing list *>>* Labs-l at lists.wikimedia.org <https://lists.wikimedia.org/mailman/listinfo/labs-l> *>>* https://lists.wikimedia.org/mailman/listinfo/labs-l <https://lists.wikimedia.org/mailman/listinfo/labs-l> *>>>>>>* _______________________________________________ *>>* Labs-l mailing list *>>* Labs-l at lists.wikimedia.org <https://lists.wikimedia.org/mailman/listinfo/labs-l> *>>* https://lists.wikimedia.org/mailman/listinfo/labs-l <https://lists.wikimedia.org/mailman/listinfo/labs-l>*
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
