You could also use a 3 "program" solution here. One program that has the
data and writes that data to a middle program (like a in-memory database
[array]) that holds the information (it runs all the time) and a third
program that collects the data from the second.
HTH
will
_________________________
William Schwartz
Network Integrator
[EMAIL PROTECTED]
----- Original Message -----
From: "Tanner, Robby" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 25, 2000 12:01 PM
Subject: RE: Creating Globally Accesable System Variables
> If you're doing this programmatically, you can spawn a child
> process, before the creating process exits, to hold the data and connect
to
> it using various IPC methods. Orphaned child processes are adopted by the
> O/S (at least for UNIX, I'm assuming Linux would do the same).
> Alternatively, you could do something quick and easy with a
> tempfile.
>
> > -----Original Message-----
> > From: Robert Canary [SMTP:[EMAIL PROTECTED]]
> > Sent: Friday, February 25, 2000 8:44 AM
> > To: [EMAIL PROTECTED]
> > Subject: Creating Globally Accesable System Variables
> >
> > Hi,
> >
> > Is there away to stick a value into memory somewhere that another
> > process can access at any given time?
> > (after the process that created the value has exited)
> >
> > --
> > robert canary
> > system services
> > OhioCounty.Net
> > [EMAIL PROTECTED]
> > (270)298-9331 Office
> > (270)298-7449 Fax
> >
> >
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
>
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
