Michael B. Eichorn wrote on 11/21/2015 21:42:
On Sat, 2015-11-21 at 13:31 +0100, Miroslav Lachman wrote:
I noticed some weird behavior of "su" command in shell scripts
running
from cron after upgrade from FreeBSD 8.4 to 10.2.
If I have this in script
su -m www -c 'ls -l'
then I get "TERM: Und
Miroslav Lachman wrote on 11/22/2015 12:03:
Michael B. Eichorn wrote on 11/21/2015 21:42:
On Sat, 2015-11-21 at 13:31 +0100, Miroslav Lachman wrote:
I noticed some weird behavior of "su" command in shell scripts
running
from cron after upgrade from FreeBSD 8.4 to 10.2.
If I have this in script
Erich Dollansky wrote on 11/23/2015 00:31:
Hi,
On Sun, 22 Nov 2015 14:04:25 +0100
Miroslav Lachman <000.f...@quip.cz> wrote:
Miroslav Lachman
The only workaround I found is adding
export TERM=""
at the top of the script.
this is a bit strange. TERM should be always define to tell the
appl
Hi,
On Sun, 22 Nov 2015 14:04:25 +0100
Miroslav Lachman <000.f...@quip.cz> wrote:
> >
> > Miroslav Lachman
>
> The only workaround I found is adding
> export TERM=""
> at the top of the script.
>
this is a bit strange. TERM should be always define to tell the
applications the capabilities of
On Sun, Nov 22, 2015 at 6:31 PM, Erich Dollansky <
erichsfreebsdl...@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; che
On Sun, 2015-11-22 at 19:43 -0500, Brandon Allbery wrote:
> On Sun, Nov 22, 2015 at 6:31 PM, Erich Dollansky <
> erichsfreebsdl...@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 c
