Taking it a little further and daemonizing, etc...
#!/usr/bin/env perl
use common::sense;
use POSIX qw//;
defined (my $pid = fork()) or die "Can't fork: $!";
exit if $pid;
chdir "$ENV{HOME}" or die "Can't chdir $ENV{HOME}";
POSIX::setsid or die "setsid: $!";
close STDOUT; close STDIN; close STDERR;
open STDIN, '<', "/dev/null" or die "open: $!";
open STDOUT, '>', "/dev/null" or die "open: $!";
open STDERR, '>', "/dev/null" or die "open: $!";
defined ($pid = fork()) or die "Can't fork: $!";
if ($pid) { waitpid $pid, 0; }
else {
eval {
my @cmd = (
'/usr/X11R6/bin/xterm',
'-e',
'/bin/sh -c "find . | xargs egrep "perl""', #simulate module loading
);
exec @cmd;
};
warn $@ if $@;
exit 1;
}
-
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
or How to display code and escape characters
are good places to start.
|