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
When an account is sorried, any current processes running as that user should be kill -9d on any machines they could potentially be running on (tsunami, death, vampires, segfault, corruption, and maybe more?).
Also, user crontabs should be disabled on these machines. Cron won't be able to run anything as the user but will still try, filling our logs with garbage. A recent compromise included adding stuff to crontab.
The text was updated successfully, but these errors were encountered:
In the new sorry we can just shell out and kill -SIGKILL everything with root/kerberos ticket, any suggestions on how to restore their cron? Just save them in sorried user's home dir...?
When an account is sorried, any current processes running as that user should be
kill -9
d on any machines they could potentially be running on (tsunami
,death
,vampires
,segfault
,corruption
, and maybe more?).Also, user crontabs should be disabled on these machines. Cron won't be able to run anything as the user but will still try, filling our logs with garbage. A recent compromise included adding stuff to crontab.
The text was updated successfully, but these errors were encountered: