You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a bug in the parameter checking code on this line
This checks to see if the user passed in a date and a user list or just a user list. The issue is that when the user provides dates in this format 030119 for example, this gets passed to the id command. If there exists a user on the system with a uid of 30119 for example, this will return true and mistakenly be taken as a user name and passed to sacct.
For example, suppose a user exists on the system:
$ id 030119
uid=30119(janedoe) gid=12345(janedoe)
This call to slogs will fail:
$ slogs 030119 testuser -X --accounts=testaccount
Retrieving accounting data for user 030119 ...
Invalid time specification (pos=0): testuser
The short term workaround is to just use a different date format like so:
$ slogs '2019-03-01' testuser -X --accounts=testaccount
Retrieving accounting data for user testuser ...
JobID User NCPUS Start Elapsed ReqMem AveRSS MaxRSS
-------------------- --------- ---------- ------------------- ---------- ---------- ---------- ----------
But the code should fixed to better test input parameters and be insensitive to date formats.
The text was updated successfully, but these errors were encountered:
There's a bug in the parameter checking code on this line
This checks to see if the user passed in a date and a user list or just a user list. The issue is that when the user provides dates in this format
030119
for example, this gets passed to theid
command. If there exists a user on the system with a uid of 30119 for example, this will return true and mistakenly be taken as a user name and passed tosacct
.For example, suppose a user exists on the system:
This call to slogs will fail:
The short term workaround is to just use a different date format like so:
But the code should fixed to better test input parameters and be insensitive to date formats.
The text was updated successfully, but these errors were encountered: