Srinivas,

I couldn't help this post. I love Perl beyond words. That said, personally I stay away from using threads with Perl. I have always thought that there were too many caveats and the consequences of failure too severe. For me, fork and exec have always gained me the kinds of control and concurrency that I have looked for when scripting. This is no doubt heretical to some/many but that's how I use the language and I won't be changing. I am just too damn productive when I am not worrying if every level underneath me is thread-safe. I understand, BTW, that there are some other CPAN approaches beyond fork and exec and I have read very nice things about them; I have merely never had cause to investigate.

Regards,
welchavw

In reply to Re: glibc error in linux by welchavw
in thread glibc error in linux by srinivas_rocks

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.