Tag Info

Hot answers tagged

2

If it works when you run it directly but not from cron there is probably something different in the environment. You can save your environment interactively by doing set | sort > env.interactive And do the same thing in your script set | sort > /tmp/env.cron And then diff /tmp/env.cron env.interactive and see what matters. Things like PATH are ...


2

If all your users have .bashrc with a reference to execute /etc/bashrc, then adding a line at the bottom of that file would be a good place to make this modification overwriting the previous alias. At the bottom of /etc/bashrc add some comments and the new alias, like: # Setting ll alias -- August 2014 # by XXXX alias ll='ls -lha --color=auto' I think ...


1

The reason you are in read-only mode is that: a) Your file system was found to be damaged, then b) Your OS tried to fix it at boot, but failed, so c) Dropped you into a read-only shell so that you can extract and backup your files without modifying original file system hence preventing you from damaging it further. If I were you, I would try to fix the ...


1

Is that the entire script? There's no 'shebang' line add #!/bin/bash to the first line if it isn't there already. Also did you mark the file executable?



Only top voted, non community-wiki answers of a minimum length are eligible