kdagraph.blogg.se

But if you're already root, su doesn't ask anything so sudo su - works.

Su - is enough to get a login shell but su asks for root's password and in ubuntu we're so used to sudo only asking for our password we don't even remember root's password. (If you do run it as root, you may later have trouble starting it yourself due to log files being only writable by root - you'll have to sudo rm them and then it'll launch also, it will default to only backing up /root/ so make sure you configure the right directorie(s).) Instead, exit the root shell and run it as yourself, as the above example shows. NOTE: when it asks you if you want to start CrashPlanDesktop, say NO. Thank you for installing CrashPlan for exit Would you like to start CrashPlanDesktop? (y/n) Let's try harder - let's work from a real root login shell, which does a more thorough reset (environment variables, directory etc.): ~/CrashPlan-install $ sudo su echo $SHELL # that wasn't the problem cd bash install.sh Standard input: sed -imod "s|Exec=.*|Exec=/usr/local/crashplan/bin/CrashPlanDesktop|" /home/anat/Desktop/sktop & rm -rf /home/anat/Desktop/sktopmod Did you mean “COMMAND and COMMAND”? See the help section for the “and” builtin command by typing “help and”. So I tried env SHELL=/bin/bash sudo bash install.sh => still same fish error! fish: Expected a command name, got token of type “Run job in background”. Normally bash install.sh or sudo bash install.sh should have worked but with CrashPlan's script indeed some internal commands end up running under fish and failing due to syntax differences.Ī common reason this may happen is the $SHELL environment variable, which still points to /usr/bin/fish - many programs execute subcommands using $SHELL.