Click here to get back home

daemonizing a process AND capture stdout, stderr
 Home | NewsGroups | Search | About
Login Password
Register Now!
 comp.lang.perl.misc    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
daemonizing a process AND capture stdout, stderr Gyruss 01-14-2005
Get Chitika Premium
Posted by Brian McCauley on January 14, 2005, 6:24 pm
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,


> There
> is a rogue carriage return (0xd) in the string

> Is there something I can do to deal with this
> situation?


Repair the corrupted file:

perl -p -i -e 'tr/\r//d' bad_file


--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas

Posted by Gyruss on January 15, 2005, 11:59 am
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,


> There
> is a rogue carriage return (0xd) in the string

> Is there something I can do to deal with this
> situation?


Repair the corrupted file:

perl -p -i -e 'tr/\r//d' bad_file


--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas

Posted by Brian McCauley on January 15, 2005, 2:45 pm
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,


> There
> is a rogue carriage return (0xd) in the string

> Is there something I can do to deal with this
> situation?


Repair the corrupted file:

perl -p -i -e 'tr/\r//d' bad_file


--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas

Similar ThreadsPosted
STDOUT and STDERR redirection fails for forked process July 19, 2007, 4:06 am
STDOUT and STDERR redirection fails for forked process July 19, 2007, 6:09 am
FAQ 8.25: How can I capture STDERR from an external command? November 1, 2004, 12:03 pm
FAQ 8.25: How can I capture STDERR from an external command? November 5, 2004, 6:03 pm
FAQ 8.25 How can I capture STDERR from an external command? March 15, 2005, 12:03 am
FAQ 8.25 How can I capture STDERR from an external command? May 24, 2005, 5:03 am
FAQ 8.25 How can I capture STDERR from an external command? August 8, 2005, 10:03 pm
FAQ 8.25 How can I capture STDERR from an external command? September 12, 2005, 4:03 pm
FAQ 8.25 How can I capture STDERR from an external command? February 6, 2006, 6:03 am
FAQ 8.25 How can I capture STDERR from an external command? June 27, 2006, 3:03 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap