GitLab

no longer waits that long.

reloading, not come all the way back up. Also, always sets
current_reloads right before calling os_select, in case it got
cleared out in the meantime.

links.

Mike. I pissed on that text, and I'm sure Mike will piss on my text.
Sorta like when Torrey pees on Maple while she is peeing. Poor girl.

case that the mysql server goes away suddenly. Defaults to 1, which
gives us the behaviour we have now. Used like this after loading libdb:

	$libdb::DBQUERY_MAXTRIES = 5;

The query will be retried this many times. For infinite retry, set it
to zero! Note that I'm not entirely sure if queries are atomic, so
beware if you use this.

Also some minor cleanup of $scriptname usage, some of which was
duplicated in the connect routine.

ports required for a machine to be a boss or ops node.

tedious, annyoing stuff from doc/setup-ops.txt .

eventually migrate into this directory in the hopes that we can
separate it from the rest of the system. Please, I know what you are
thinking.

a couple of instances that will cause a failure).  My check for overfilling
was wrong anyway, it didn't take into account the header.

Have imagedump print a couple of counts as unsigned.

The practical effect was that new passwords were still using the
ancient crypt algorithm, while new users were getting modern crypt.

snuck back in while I was sleeping last night. Boy, was that a good
nights sleep. Dreams of cars and trains and video cameras ...

a restart experiment option.

audited using libaudit. No more batchmode since the script is
generally very fast anyway. Remove all the sendmail stuff since that
is done by the audit library.

Get rid of fork since I learned from Mike that perl does proper EUID
flipping.

audited using libaudit. No more batchmode since the script is
generally very fast anyway. Remove all the sendmail stuff since that
is done by the audit library.

Also a bunch of cleanup and error handling.

audited using libaudit. No more batchmode since the script is
generally very fast anyway. Remove all the sendmail stuff since that
is done by the audit library.

audited using libaudit. No more batchmode since the script is
generally very fast anyway. Remove all the sendmail stuff since that
is done by the audit library.

Add lots more error checking. Moved the DB changes from the web
interface into this script.

Did you know that pw groupdel wrongly returns 65 when a group does
not exist, instead of 67 as the man page says?

a call to existing routine in showstuff. Also changed the interface
to SHOWGROUPMEMBERS() so that priv people get a "remove from project"
option when showing the default group membership. Yes, project leaders
can now delete users from their project.

ssh, sfs key options. Admin types also get freeze/thaw and delete
options.

Kill the modify/delete buttons. Silly. Do it through the user's
page now.

talked about it and never did anything. I bet Mike knows though.

with the deleteuser change! Sorry.

and replace with script to delete a user, either from a single project
or from the entire testbed. All of the DB stuff is done in the script;
the web interface no longer does anything but error checks. This is
because removing a user requires some finess in when things are
removed, and if there are any failures I wanted to make sure that the
script could be rerun on a user, without barfing.

Add lots of error checks to make sure not deleting a user who is
"important" (project head, group head, experiment head, etc).

Add "request" mode. If a project leader deletes a user from his
project, and the user has no more project memberships, show a click
button to send us email requesting the user be deleted from the
testbed.

Bottom line, project leaders can now delete users from their project,
but must ask us to delete the account from the testbed.

project and the account is removed. Add some better warm fuzzies.
Also some changes to command line args to backend scripts.

all the DB changes to the script. Add more error checks. Remove mail,
since thats done in the backend now.

output from the script. Cleanup formatting when there is output.

stuff from the web interface (which only does error checks now) into
the script, and reorg so that errors do not result in inconsistent DB
state that would prevent the script from being run a second time after
failure. Note that rmproj does not remove users.