Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Ilya,

Great article, really useful. I think cybear was joking btw.

One thing that tripped me up when trying to send multiple processes to a series of ttys: DB::get_fork_TTY is called from the child, after the fork. So, this won't work:

{ my $ttyno = 1; sub DB::get_fork_TTY{ $DB::fork_TTY = "/dev/pts/" . $ttyno++; } }

because the $ttyno is in separate processes. Instead, redefine your $ttyno after the fork:

use vars $ttyno; for my $fork (0 .. $forks) { if (fork) { } else { # in child $ttyno = $fork; } } sub DB::get_fork_TTY { $DB::fork_TTY = "/dev/pts/" . $main::tty; }

dave hj~


In reply to Re: Debugging Perl scripts which use fork() by dash2
in thread Debugging Perl scripts which use fork() by IlyaM

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.