Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Presented by
Date
LAVA Lab
Orphan Hacking Sessions
Dave Pigott
12 February 2015
What’s the problem?
● Hacking sessions with long
timeouts
● People forget to do “stop_hacking”
● Devices are busy doing no...
How can we fix it? Some ideas...
● Look for idle time > t
● Look for no user logged in > t
● Put out regular console messa...
HKG15-402: Orphan hacking sessions
Upcoming SlideShare
Loading in …5
×

HKG15-402: Orphan hacking sessions

1,346 views

Published on

HKG15-402: Orphan hacking sessions
---------------------------------------------------
Speaker: Dave Pigott
Date: February 12, 2015
---------------------------------------------------
★ Session Summary ★
One of the problems we experience quite a lot is to do with people setting inordinately long timeouts on their hacking sessions, which leaves the board unavailable for queued jobs. This session is to explore some of the possible solutions, in LAVA, the Lab and the general v.l.o community of users. Some possible scenarios are: - you have to specify in the job that if you leave the ssh session, you want to keep hacking up for later - if a hacking session detects that there are no users ssh’d in for a defined period of tim
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250829
Video: https://www.youtube.com/watch?v=yY8bF9dGVn4
Etherpad: http://pad.linaro.org/p/hkg15-402
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org

Published in: Software
  • Be the first to comment

  • Be the first to like this

HKG15-402: Orphan hacking sessions

  1. 1. Presented by Date LAVA Lab Orphan Hacking Sessions Dave Pigott 12 February 2015
  2. 2. What’s the problem? ● Hacking sessions with long timeouts ● People forget to do “stop_hacking” ● Devices are busy doing nothing ○ Resources are reduced ○ Sometimes only one device type
  3. 3. How can we fix it? Some ideas... ● Look for idle time > t ● Look for no user logged in > t ● Put out regular console messages ○ who ○ ps aux ● And…?

×