SUMMARY: /etc/project woes

From: Christopher Barnard <>
Date: Sun Sep 18 2011 - 21:45:49 EDT
I asked:

> I recently made some changes to the /etc/project file on one of my Solaris
> servers.  But now users have to authenticate *twice* to see the changes to
> project file.  Now I know that if I reboot the server it will work
> But this is a Sun, not a @#)(*@()&#^ Windows box.  I shouldn't have to
> to enable this...
> Is there a way to get the changes to this file to take effect short of
> rebooting?
> ----------------------------8<---------------------------------
> sandbox : /opt/home/cbarnard$ ssh -l epicadm
>'s password:
> Last login: Mon Aug 29 18:27:58 2011 from
> epicadm@servername$ id -p
> uid=25630(epicadm) gid=101(epicsys) projid=0(system)
> epicadm@servername$ /bin/su - epicadm
> Password:
> epicadm@servername$ id -p
> uid=25630(epicadm) gid=101(epicsys) projid=102(user.epicadm)
> epicadm@servername$
> --------------------------8<----------------------------------------

The answer:

no, a reboot would not fix the issue.  I only got one response, but it was
right on the head.  SunSSH vs OpenSSH.  The /etc/project file is something
unique to Suns and so only SunSSH honors it.  OpenSSH does not.  This is
inadvertently enforcing security rules concerning shared accounts, so I do not
mind.  su does honor the /etc/project file, so in order for these databases to
work properly, the DBAs must log on as themselves and then su to the shared
user that runs the database.  Win win, I say.

Thanks to
 Martin, Jeff <>

Christopher L. Barnard
comment your code as if the maintainer is a homicidal maniac who knows where
you live.
sunmanagers mailing list
Received on Sun Sep 18 21:46:17 2011

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:18 EST