Oleksandr Gavenko <gaven...@gmail.com> writes: > > I strongly suggest remove 'system' call to avoid 'sh -c' execution. Instead > use 'exec' without 'fork' to free CPU and memory from '/usr/bin/perl > /usr/bin/see'.
You mean not run /bin/sh but instead spawn the command directly? RFC1524 under "Semantics of executable commands" says it's supposed to be /bin/sh, ... it is specified that the command line be intended as input to the Bourne shell, i.e., that it is implicitly preceded by "/bin/sh -c " on the command line.) It might be possible to sometimes notice that the shell is not required for a particular command form. That might even be the majority of commands. But my inclination would be not to worry about the extra. Alternatively, if you meant that run-mailcap itself could exec the /bin/sh, thereby not having a running perl waiting -- then maybe that could be done if run-mailcap hasn't made any temporary files. You'd lose the warning message printed if the command fails, but maybe there's a command-not-found message from the shell anyway in that case. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
