chuser(1) - man page
Name
chuser- change the current user
Synopsis
chuser [options]
Options
-n, --now immediately terminate this user.
-s, --soft if painless termination protocols are available,
use them. This option is ignored on systems without
appropriate hardware.
-R, --recursive terminate users recursively. This option causes
chuser to spawn new chuser processes repeatedly
until a user capable of terminating it does so.
-v, --verbose replace the usual output of chuser with the
input from the microphone.
History
chuser is intended for users who are instructed to use it by
remote helpdesk operators. It is scheduled for depre-
cation when IT customer services are replaced by robots
with infinite patience.
Comments
chuser attempts to detach the current user from the current
machine. The result of running chuser is non-deterministic
and depends on available hardware. chuser typically fails when run
by a user who intended to run it, but may succeed when used
unwittingly.
chuser expects to run on a foreground thread, so attempting
to background it or run it in a terminal controlled by screen(1)
or tmux(1) may increase the chance of success.
See also
shutdown(8)
kill(1)
sudo rm -Rf /
[RequireClaim()] Attribute for Claims-based Authorization Asp.Net Core
Appears to be irritatingly missing. So I did https://github.com/chrisfcarroll/RequireClaimAttributeAspNetCore
iTunes Home Sharing doesn’t work with AppleTV when it should
For about a year, I've been stumped on iTunes Sharing not working on AppleTV when it worked fine between laptops. Until today, when I accidentally discovered that iTunes -> Preferences -> Sharing -> "Share Library on Network" —which works for computers running iTunes— is not the same things as iTunes -> File -> Home Sharing, which is what AppleTV uses.
Oh well.
‘bash\r’: No such file or directory. Or, editing unix files on a Windows machine
'bash\r': No such file or directory
What does that mean, you ask yourself? It usually means you are editing *nix script files on a windows system, and then running the files on a *nix machine. For instance in docker, or a VM.
Your GUI solution is to use a text editor that allows you to save with unix line endings. `Notepad++` calls it, very reasonably, `'EOL conversion'`. Sublime text calls it `View->Line Endings`.
Your commandline solution in a bash shell on macos is sed -i.bak $'s/\r//' * and on linux the same but you don't need the ansi-C quoting: sed -i.bak 's/\r//' *
A further complication if you are using git is that it keeps getting reset back to windows. You could fix this with `git config core.autocrlf false` but that may have other consequences which you don't want to bother with.