On Sun, Nov 22, 2015 at 6:31 PM, Erich Dollansky < erichsfreebsdlist at alogt.com> wrote:> this is a bit strange. TERM should be always define to tell the > applications the capabilities of your terminal. >Things run from crontab don't have a terminal. I note the error message looks like csh; check the target user's .cshrc. -- brandon s allbery kf8nh sine nomine associates allbery.b at gmail.com ballbery at sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
On Sun, 2015-11-22 at 19:43 -0500, Brandon Allbery wrote:> On Sun, Nov 22, 2015 at 6:31 PM, Erich Dollansky < > erichsfreebsdlist at alogt.com> wrote: > > > this is a bit strange. TERM should be always define to tell the > > applications the capabilities of your terminal. > > > > Things run from crontab don't have a terminal.Indeed cron only sets SHELL HOME PATH and USER> > I note the error message looks like csh; check the target user's > .cshrc. >but we are running from cron which defaults to sh inside a script with a #!/bin/sh and the call is su -m which should leave the environment unmodified and use the current shell (presumably still sh) as the login shell. Also www has a home of /nonexistant, no .cshrc file to be had. Maybe freebsd-update IDS is in order? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5729 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20151122/833d1108/attachment.bin>