4,684 reputation
11323
bio website keith-s-thompson.github.com
location San Diego, CA
age 54
visits member for 2 years, 11 months
seen 16 hours ago

I'm a programmer and all-around nerd living in San Diego, California.
I work at JetHead Development Inc.

E-mail: Keith.S.Thompson@gmail.com


Feb
4
comment cd ${DIR_PATH} returns 'No such file or directory'
Copy-the following as a single line and paste it to your shell prompt: export DIR_PATH=~/concrete/path ; echo DIR_PATH=${DIR_PATH} ; cd ${DIR_PATH} ; pwd
Feb
4
comment cd ${DIR_PATH} returns 'No such file or directory'
That's odd; it works for me on Linux with bash 3.2.25 and 4.2.37. What does echo $BASH_VERSION print?
Feb
4
comment cd ${DIR_PATH} returns 'No such file or directory'
I'm surprised that worked. As far as I know, bash will replace ~ by your home directory path, whether it's in .bash_profile or not. I can imagine the expansion not working immediately after an =, but experiment with bash 3.2.25 and 4.2.37 indicates that that does work. What happens when you use $HOME rather than ~? If that works, it would be a better solution.
Feb
3
comment Installing as 'root' is not currently supported - what should I do?
@Perlnika: Ok, but you might still be able to create the smrtanalysis user account on your system. The configuration of /home prevents you from doing it straightforwardly, but you should be able to give the account a home directory somewhere else (that won't be shared with other nodes).
Feb
3
comment Installing as 'root' is not currently supported - what should I do?
@Perlnika: Then you're not following the installer's advice, which is to install the software as a dedicated user such as smrtanalysis, not as yourself. I'm not saying you have to do that, but if you're going to ignore that advice, be sure you have a good reason for doing so.
Feb
3
revised Is there a graphical shell or scripting environment for Linux?
Link to Yahoo Pipes, fix typo
Feb
3
comment Installing as 'root' is not currently supported - what should I do?
@cjm: The $ in the prompt probably implies that he's running as a non-root user, as does the fact that the "finally" got root access (so he must have had a non-root account before). It's just the phrase "my own user - which is root" which is confusing, and possibly misleading.
Feb
3
revised Installing as 'root' is not currently supported - what should I do?
lang-none
Feb
3
answered Installing as 'root' is not currently supported - what should I do?
Jan
24
comment What features are in zsh and missing from bash, or vice versa?
Bash does this, at least as of version 4.2.37; it replaces newlines by semicolons and gives you a single line to edit.
Jan
22
revised Bash autocompletion for an environment variable holding a directory name
added 244 characters in body
Jan
22
comment Bash autocompletion for an environment variable holding a directory name
@l0b0: (a) I already have it. (b) I'm not feeling quite that adventurous. (c) It's suppose to be programmable completion.
Jan
22
asked Bash autocompletion for an environment variable holding a directory name
Jan
18
comment sh script will not execute as root (cron)
Ah, after reformatting I see that that's a root shell prompt after the crontab output.
Jan
18
revised sh script will not execute as root (cron)
Formatting
Jan
18
comment sh script will not execute as root (cron)
You wrote cronjob -l. There is no cronjob command. Did you mean crontab -l? The #!/bin/bash at the top of your script is correct, but then the correct way to invoke it is just /root/miami.sh, not /bin/sh /root/miami.sh; you should remove the /bin/sh from your cron job. Is the stuff in your question after the incorrect cronjob line the output of crontab -l? Did you run crontab -l as the root user? You refer to both thescriptname.sh and miami.sh; if those refer to the same thing, please update your question to be more consistent.
Jan
18
comment sh script will not execute as root (cron)
What is cronjob -e? What is the output of crontab -l executed as root? Why does a bash script have a .sh suffix, and why are you executing it with /bin/sh rather than running it directly? You're using some bash-specific features that /bin/sh may or may not support, but there's not enough information to know whether that's the problem.
Jan
18
revised sh script will not execute as root (cron)
Formatting
Jan
18
comment sh script will not execute as root (cron)
Also posted here on Stack Overflow.
Jan
18
comment How to restrict rm -rf / in CentOS machine?
Not running as root should prevent most of the harm that rm -rf / would otherwise do.