13 Apr
2010
13 Apr
'10
3:18 a.m.
Hi,
I'm just upgraded a system from a prior debian to the recent one (from etch /4.0 to lenny/5.0 ) and I had a script which is run by inetd.
it was worked so far, but now it outputs a null byte (\0) to the stdout even if the script does not writes to the stdout.
if I run the _SAME_ script on an older system, it works no null byte, from Shell, it works, again no leading null byte. just from inetd. I also tried to change bsd inetd to rlinetd, same effect.
do you have any idea what makes that extra null byte?
Thanks, Redax