Thanks to everyone for the quick responses:
Jie Gao [J.Gao_at_isu.usyd.edu.au]
Santosh Krishnan x2815 [santosh_at_heplinux1.uta.edu]
Robert Kubarych [rkubaryc_at_sunyrockland.edu]
Lars Bro [lbr_at_dksin.dk]
Dejan Muhamedagic [dejan_at_yunix.co.yu]
Whitney Latta [latta_at_decatl.alf.dec.com]
Biggerstaff, Craig T
[Craig.T.Biggerstaff_at_USAHQ.UnitedSpaceAlliance.com]
Lars and Jie came up with the solution:
System V UNIX sets the group as of the process. BSD (Digital Unix)
does not. It is tunable with the variable sys_v_mode (you can set it
to 1). But you should preferably consult System V Compatibility Userīs
Guide to see the other things that will change when you set this. See
open(2), mknod(2) and mkdir (2).
It can be changed by adding
sys_v_mode 1
to your /usr/sys/conf/<SYSTEM> file and rebuild the kernel.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Original Post:
Hello all,
This is probably a simple one.
/tmp under Solaris is setup by default drwxrwxrwt
Any file written to this directory has the permissions according to
the umask and the user as the owner and the users primary group id as
the group.
On digital unix it is the same only the group of the file created is
NOT the users primary group (which I'd prefer it to be) - rather it is
the group of whatever the parent directory is set to - ie if /tmp has
group sys - all files in the /tmp are set to group sys unless you
explicitly do a chgrp on them.
Anyone know why this happens and if there is a fix?
TIA
Sue
Sue Gray
sjgray_at_subcorp.com.au
Network Analyst
A.S.C.
Received on Thu Sep 10 1998 - 23:58:50 NZST