tg d415592b37 check return value of unlink(2) when trying to remove an existing HISTFILE,
since mksh(1) did go into an infinite loop if that fails first

bug spotted, initial patch and help drafting a test case
From: Decklin Foster <decklin@red-bean.com>

note there are more instances of unlink(2) and others (like chmod(2), as
spotted by flawfinder) which aren’t checked… but at least the other case
of unlink(2) use in histrap.c doesn’t cause any trouble (I think)
2008-07-06 22:41:09 +00:00
2007-06-05 18:59:54 +00:00
2008-06-08 17:16:25 +00:00
2008-04-19 22:15:06 +00:00
Description
MirBSD Korn Shell for Jehanne
6.7 MiB
Languages
C 57.6%
Shell 26%
Roff 13.3%
Perl 2.6%
Makefile 0.5%