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.
Note that similar behavior existed between f50473e and 3822032, but the
new proposed behavior does not generate error.
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxx
Lihovarská 1060/12 tel: +49 911 7405384547
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
--
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
