Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • You don't need a sysadmin to set up inetd for you. Just write your own configuration file and do:

          % /usr/sbin/inetd ~/my-inetd.conf

    So long as the port you are using isn't below 1024 there shouldn't be any problem.

    BTW, if your sysadmin notices two copies of inetd running, she may start getting confused, so it's probably an idea to let her know what you're doing even though it's perfectly reasonable.

    -Dom
    • BTW, if your sysadmin notices two copies of inetd running, she may start getting confused, so it's probably an idea to let her know what you're doing even though it's perfectly reasonable.

      Yep. That's another advantage of the wrapper script. :)

      I think I did the personally run inetd a couple of years back, but the wrapper I've written with the DummyInetd module makes it easier because I don't have to do any setup. It's just ./inetd path/to/program. Also, don't you still have to configure /etc/servic

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers