Date: Mon, 14 Aug 1995 17:57:01 +0200 From: Wolfram Schneider <wosch@cs.tu-berlin.de> To: Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu> Cc: FreeBSD-bugs@freebsd.org Subject: bin/683: cron(8) Message-ID: <199508141557.RAA14439@caramba.cs.tu-berlin.de> In-Reply-To: <9508141532.AA11236@halloran-eldar.lcs.mit.edu> References: <199508131617.SAA13412@localhost> <9508141442.AA11143@halloran-eldar.lcs.mit.edu> <199508141459.QAA11761@caramba.cs.tu-berlin.de> <9508141532.AA11236@halloran-eldar.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Wollman writes: >You missed the point. It is none of cron's business to be parsing >shell command lines, period. > >What should cron do with this: > >------------------------------------ >SHELL=/usr/site/bin/bash >30 4 1 * * help >------------------------------------ > >Or how about this: > >------------------------------------ >SHELL=/usr/local/bin/foosh >15 0 * * */2 grimblepritz garply foobiebletch >------------------------------------ >(where in the `foosh' language, `garply' means the same as `>' in >Bourne shell) > >You are putting knowledge into utility programs which have no business >applying them; this is simply the Wrong Thing. Ok, ok. Add a check for $SHELL (/bin/sh or /bin/csh). Carefully users don't put shell builtin's into crontab or uses funny shells (grimblepritz, emacs, perl etc.) Wolfram
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508141557.RAA14439>