/proc is highly OS dependant and on most systems, AFAIK, only for communication with the kernel.
If you are writting some network server in a non blocking fashion (so, using select), you can use another TCP port or a Unix socket to serve the status (or if it is a web server, mapping it to a specific url).
If performance is what bothers you, you can use some shared memory module or use a ram file system (for instance, /tmp on Solaris).
You can also write status to disk only when a signal is sent to the process, but be carefull on how you handle signals from perl because it is easy to crash the app if you try to do something complex there that allocates memory.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.