11-28-2019
Welcome Simon. I too have noticed your excellent contributions over a long period of time.
3 More Discussions You Might Find Interesting
1. What is on Your Mind?
:) i have made new title for myself since i am very serious about unix I thought that it might reflect this a little and also help me to gain some more self esteem to be more dillegent in my questions and answers to others.. I have an avatar but I am not quite sure how to apply it. if any moderator... (5 Replies)
Discussion started by: moxxx68
5 Replies
2. What is on Your Mind?
Dear All,
I am very pleased to inform everyone that Nicki Paul (zxmaus) is joining the Moderation Team after a number of years away from the site.
Nicki used to be very active here (over 800 posts), and she got busy with travel, work, family and her dogs, and we have missed her. Now she is... (7 Replies)
Discussion started by: Neo
7 Replies
3. What is on Your Mind?
Dear All,
I am very pleased to announce that Dave Munro (gull04) is joining the Moderation Team, after being a very valuable member of UNIX.com for 15+ years.
Dave is an IT Consultant with 30 years of experience this year, has worked in many of the industry vertical market segments and has... (6 Replies)
Discussion started by: Neo
6 Replies
ENV(3) Library Functions Manual ENV(3)
NAME
env - environment variables
SYNOPSIS
bind #e /env
/env/var1
/env/var2
...
DESCRIPTION
The env device serves a one-level directory containing files with arbitrary names and contents. The intention is that the file name is the
name of an environment variable (see rc(1)), and the content is the variable's current value.
When a fork(2) system call creates a new process, both the parent and the child continue to see exactly the same files in the env device:
changes made in either process can be noticed by the other. In contrast, an rfork system call with the RFENVG bit set (see fork(2)) causes
a split: initially both process groups see the same environment files, but any changes made in one process group cannot be noticed by the
other. An rfork with RFCENVG splits and then clears the environment.
SEE ALSO
rc(1), fork(2)
SOURCE
/sys/src/9/port/devenv.c
BUGS
A write starting at an offset after the current extent of a file yields an error instead of zero filling.
ENV(3)