-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: GECOS -> GECOS and Group #299
Comments
nice!! I'll discuss with Fotis, but I think we could add that! |
surely yes!!
|
@stetner @fgeorgatos fixed in experimental branch. |
I am getting 0 for all groups:
Other than that it looks good - the colors with background are now displaying properly as well! What can I do to get you some data on why the group os not working? BTW I will be away Sept 4-15th so will not update in that period. Thanks, |
Oh, and also no GECOS name with or without a ~/.local/qtop/getent_passwd.txt file |
BTW - since my environment is LDAP across a university, if we do an id -nG on every user, it will take 3+ minutes to return all groups. I think it would be better to iterate over the userids that are running/queueing jobs only. |
@stetner the branch is highly experimental, so it's far from being stable yet. Unfortunately, I don't have a lot of time to work on it anymore. I made some changes, if you're willing to test it it would be great! No hurry, after you get back. Concerning the LDAP thing, I'll implement it as suggested, makes sense. |
Hi Sotiris,
Lately I have been adding this to my qtop.py:
Which splits the GECOS field into a GECOS and Group field and gives me this output (qtop -aGF) that I find useful to see what group is dominating the cluster.
Any chance of getting something similar added into the official line? There is probably a more efficient way of doing it...
Doug
The text was updated successfully, but these errors were encountered: