UNIX for Dummies Questions & Answers

I want to do these commands in a script:
if the user name is 'toto' then the user switch to the group toto_group and then 2 others scripts are launched.
Unfortunately, after the command 'newgrp' the 2 scripts are not launched correctly.
But if I do the same, by hand, one line per one line, it works!! Why ?? I work on with a SUNOS5.7

Thanks for your help !

I am not getting your problem, it would be nice if you can post your code here

Regards
JK

Yes, my code is:

#! /bin/csh

set PATH_CPT = `pwd`;
set PRJ = '/home/myproject/'
echo "Changement de groupe UNIX touareg"
newgrp my_project &
## creation of the ANABE_CFG directory
if !( -d $PATH_CPT/ANABE_CFG ) then
mkdir $PATH_CPT/ANABE_CFG
cd $PATH_CPT/ANABE_CFG
mkdir CALIBRE
mkdir PROJECT
else echo " $PATH_CPT/ANABE_CFG directory already exists "
endif

stconf

icfb&

The newgrp command fires up a subshell. When you run it by hand, the subshell reads the next commands. You are running newgrp in a script. The script continues to read the commands while the subshell does nothing.


You don't need newgrp anymore. It was needed when you could only be in one group at a time. Now you can be in many at a time. Type "groups" to see your list.

newgrp has been obsolete for over a decade. But this is the second question on newgrp in the past few weeks.

There's a good reason for that. Guess the OP didn't catch it the first time you said this command is obsolete.

https://www.unix.com/showthread.php?s...ghlight=newgrp

Yes, you said that the command is obsolete but I don't know haw to do what I want !!

To secure the account of my project we create a 'subroup'. So, everybody in the team belongs to group A but few persons belongs to group B. So that the UNIX right are not the same for everybody. If everybody can read all datas, only few persons are authorised to write on the project account. To do that, I though to use the command newgrp. When we work for the project, before launching applications, we do newgrp.

How can I do that without (or with ??) using newgrp ??!!

Thanks

Nathe

For newgrp to work, the user must be listed in the group entry. But if the user is listed in the group entry, the login program will make the user a member of the group at login time. Thus newgrp is a no-op. I just tested this on Solaris. Try it yourself:
groups
newgrp somegrp
groups
This might be useful is a user was recently added to a group, I suppose. But the user some just sign off and on again. Or exec login or something.

Or you could be using group passwords. But there is no tool to assign them. Did you write one or something? There is no equivalent of /etc/shadow for group passwords. You would be leaving the encrypted password in plain sight. The manpage for newgrp warns against using group passwords. Group passwords were deprecated over a quarter of a century ago.

Doing what you want is trivial. I can't imagine how your got it work with newgrp but arranged for it to not work without newgroup. In fact, I strongly suspect that you are finished, but don't know it.

Everyone is in groupa. A few people are in groupb. Now you do:
chgrp groupb somefile
chmod 464 somefile

Now everyone can read somefile. Those folks (and only those folks) in groupb can write it. And all the groupb people need to do is logon. Forget about newgrp. It is that simple.