nguyenmp / csil_status Goto Github PK

The host file contains all IP addresses and hostnames of all DHCP servers and even private computers used in ISEC labs and stuff. Lets avoid probing those computers.

My suggestion is only probing the 128.111.43/24 network mask.

See title. We can use linux13.engr.ucsb.edu as a homebase to grab the /etc/hosts

It would be nice if LoadAvg output listed the most available (lowest system load) machines toward the top, while machines with higher system load averages were listed toward the bottom. This would allow the user to easily choose a good machine to use.

Perhaps there should be some sort of ranking equation that, based on the load averages provided (1 minute, 5 minute, and 10 minute) decides what machines are most free for use.

Given the number of machines ECI users have access to, it could be useful to gather metrics on each one, such as number of currently logged on users, hardware capabilities, CPU load, and more. This would help users intelligently choose which machine to run intensive processes on for maximum performance, all while minimizing disruption to other users.

We can add (non-interactive) commands using ChannelExec from JSch

Slightly referenced in Issue #2...

I've been digging around. It looks like I just really want to parse who and w command outputs.

I've finally gotten stable outputs from w -oui which basically resolves hostnames and forces the "from" field to always show.