Hi:
> From: "Eduardo Tongson" <[EMAIL PROTECTED]>
>
> Hi Ludwig,
>
> A brief warning. Readonly variables are not meant for
> limiting/securing shell use.
> This is easily subverted with subshells, absolute paths
> and by
> completely ignoring built-in functions.
>
> What do you want to achieve by preventing modification of
> environment variables?
>
Sorry for the late reply. I'm using it as a part of
software development. Unix IPCs such as message queues and
shared memory are dependent on temp files. I plan to
place the value of a file directory in an enviroment
variable.
Example : process A runs , after some time process B
runs. Both access the same enviroment variable. What I want
to avoid is that after process A is running and before
process B starts the value of the enviroment variable is intact.
____________________________________________________________________________________
Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
