Tukukkk

I'm currently using > /dev/null & to have Perl script A run Perl script B totally independently, and it works fine. Script B runs without throwing back any output and stays alive when Script A ends, even when my terminal session ends.

Not saying I need it, but is there a way to recapture its output if I wanted to?

Thanks

Your code framework may look like this:

#!/usr/bin/perl

# I'm a.pl

#...

system "b.pl > ~/b.out &";

while (1)

{

    my $time = localtime;

    my ($fsize, $mtime) = (stat "/var/log/syslog")[7,9];

    print "syslog: size=$fsize, mtime=$mtime at $timen";

    sleep 60;

}

while the b.pl may look like:

#!/usr/bin/perl

# I'm b.pl

while (1)

{

    my $time = localtime;

    my $fsize_a = (stat "/var/log/auth.log")[7];

    my $fsize_s = (stat "/var/log/syslog")[7];

    print "fsize: syslog=$fsize_s auth.log=$fsize_a at $timen";

    sleep 60;

}

• a.pl and b.pl do their job independently.


• b.pl is called by a.pl as a background job, which sends its output to b.out(won't mess up the screen of a.pl)


• You can read b.out from some other terminal, or after a.pl is finished(or when a.pl is put to background temporarily)

About terminating the two scripts:

• `ctrl-c` for a.pl
  


• `killall b.pl` for b.pl
  

Note:

• b.pl will never terminate even when you terminate your terminal (Assumed that your terminal is run as a desktop application), so you don't need the `nohup` command to help. (Perhaps only useful in console)
  


• If your b.pl may spit out error messages from time to time, then you still need to deal with its stderr. It's left as your homework.