Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re^2: Finding out by one process a filename opened by another process.

by Jeppe (Monk)
on Aug 01, 2012 at 10:52 UTC ( #984762=note: print w/ replies, xml ) Need Help??


in reply to Re: Finding out by one process a filename opened by another process.
in thread Finding out by one process a filename opened by another process.

Upon further consideration, it looks to me like you might want to simply build a perl package with system constants, or use a system-wide configuration file, depending upon what precisely your application does.

Using shared memory is also an option if the name of the pipe will change, the server application will then write the filename of the pipe to shared memory with a pre-determined shared memory key, and the client will then read the value from shared memory. IPC::ShareLite may be all you need.


Comment on Re^2: Finding out by one process a filename opened by another process.
Re^3: Finding out by one process a filename opened by another process.
by humble (Acolyte) on Aug 01, 2012 at 15:52 UTC
    Another approach is to write the filename (w/ its path) to a file - by forked process, then another process (waiting for the keypress) will simply read the file and get the filename w/ its path. - But I do like it because app. optimimum - that I prefer - forked process will write each file as it processes it, where waiting for key press - only now and then will use the file.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://984762]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (10)
As of 2014-12-26 07:18 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (167 votes), past polls