Re: Non-interactive shell and /dev/null

Try KDE wrote: > I noticed some shell script, for example those under /etc/cron.*/, uses > "command > /dev/null" style. I think it's because they know the scripts > is run under non-interactive shell. My question is, what would happen if > ">/dev/nul

Re: Non-interactive shell and /dev/null

Try KDE said: > Hi Everyone, > > I noticed some shell script, for example those under /etc/cron.*/, uses > "command > /dev/null" style. I think it's because they know the scripts > is run under non-interactive shell. My question is, what would happen if > &qu

Non-interactive shell and /dev/null

Hi Everyone, I noticed some shell script, for example those under /etc/cron.*/, uses "command > /dev/null" style. I think it's because they know the scripts is run under non-interactive shell. My question is, what would happen if ">/dev/null" is removed

Re: non-interactive shell

>> "SB" == Sibuyas Bombay <[EMAIL PROTECTED]> writes: SB> i don't want to give them a fully interactive shell so i was SB> thinking of writing a script that gets started when they log on SB> and will just present them with 4 choices, pon (w/ sudo), poff (w/ SB> sudo), elm, and quit(log-out). I b

non-interactive shell

hi all, i have a few users in my box that i want to give access only to a very limitted number of commands, that is, /usr/bin/pon, /usr/bin/poff and /usr/bin/elm . i don't want to give them a fully interactive shell so i was thinking of writing a script that gets started when they log on and w