Click here to get back home

Dealing With Zombies in a Daemon
 Home | NewsGroups | Search | About
Login Password
Register Now! Lost Password?
 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
Dealing With Zombies in a Daemon Hal Vaughan 08-29-2005
Get Chitika Premium
Posted by Hal Vaughan on August 29, 2005, 8:05 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 xhoster on August 30, 2005, 1:31 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 Dan Wilga on August 31, 2005, 12:10 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 Hal Vaughan on September 1, 2005, 12:27 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

Similar ThreadsPosted
Daemon Win32::Daemon; September 7, 2006, 6:58 am
FAQ 8.40: How do I avoid zombies on a Unix system? December 18, 2004, 12:03 am
FAQ 8.40 How do I avoid zombies on a Unix system? March 25, 2005, 6:03 am
FAQ 8.40 How do I avoid zombies on a Unix system? May 24, 2005, 11:03 pm
FAQ 8.40 How do I avoid zombies on a Unix system? August 9, 2005, 4:03 am
FAQ 8.40 How do I avoid zombies on a Unix system? September 11, 2005, 10:03 pm
FAQ 8.40 How do I avoid zombies on a Unix system? November 3, 2005, 5:03 am
FAQ 8.40 How do I avoid zombies on a Unix system? September 10, 2006, 9:03 pm
FAQ 8.40 How do I avoid zombies on a Unix system? June 10, 2007, 3:03 am
FAQ 8.40 How do I avoid zombies on a Unix system? November 14, 2007, 3:03 pm

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap