On Tue, Feb 10, 2015 at 10:30:35PM +0100, Stanislav Brabec wrote:
> Many people use script in their shell initialization files. It has some
> unwanted consequences, e. g. logging commands from cron (and starting them
> in a pseudo-terminal and interactive shell). It could also result in a
> seemingly hanging applications:
>
> For example:
>
> echo -e './script\nTERM=linux mutt' | \
> at $(date -d "+1 minute 5 seconds" +%H:%M)
>
> mutt will "hang" inside at, because it thinks that it is running in an
> interactive shell and waits for input.
>
> That is why I wrote --interactive command line option. If it is set, script
> called from a non-interactive session will not log anything, just
> (optionally) execute -c argument and silently exit.
Would be better to learn people to fix their shell initialization
files to not call script(1) for non-interactive sessions?
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
