Ronald F. Guilmette
2013-May-10 20:59 UTC
bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154 It has been suggested to me (by a committer) that I should raise the issue of this PR here on these lists, because the problem described within the PR remains a real problem, and despite my having proposed something that seems to be a perfectly workable fix, no action has been taken on this PR for some years now. Regards, rfg P.S. The following additional PRs, also filed by me and also relating to the script(1) command, supply some additional improvements to efficiency and code clarity. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152131 http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152132
Kurt Jaeger
2013-May-10 21:36 UTC
bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)
Hi!> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154 > > It has been suggested to me (by a committer) that I should raise the > issue of this PR here on these lists, because the problem described > within the PR remains a real problem, and despite my having proposed > something that seems to be a perfectly workable fix, no action has > been taken on this PR for some years now.Having looked at the PR, may I suggest that you look at sysutils/screen and screen -L especially instead of script -k -- and add some input logging to screen ? Or, for the tmux fraction, at sysutils/tmux ? I'm not sure why you absolutly *need* the input logging -- can you describe the use case ? Is it some security-audit-issue ? -- pi at opsec.eu +49 171 3101372 7 years to go !
Eitan Adler
2013-May-11 22:54 UTC
bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)
On 10 May 2013 16:59, Ronald F. Guilmette <rfg at tristatelogic.com> wrote:> > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154 > > It has been suggested to me (by a committer) that I should raise the > issue of this PR here on these lists, because the problem described > within the PR remains a real problem, and despite my having proposed > something that seems to be a perfectly workable fix, no action has > been taken on this PR for some years now.By the way, it will go a long way to helping get some site on these PRs, if you provide diffs in 'unified diff' form (diff -u) instead of context diff form. I have been recently looking for old PRs with patches attached. :) -- Eitan Adler _______________________________________________ freebsd-current at freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"