iw-home permissions Solaris 10 TS 6.7.1

We just installed TS 6.7.1 on Solaris 10 and when trying to access files within iw-home over telnet I see the user group is iwts and I cant access it? Is this typical?

Also we're migrating from a windows environment. Can Samba be used to access iw-home config files from a windows client. I did not find detail in the doc on the iw-home permissions or accessing config files through samba.

Find more posts tagged with

Comments

Adam Stoller

We just installed TS 6.7.1 on Solaris 10 and when trying to access files within iw-home over telnet I see the user group is iwts and I cant access it? Is this typical?

Also we're migrating from a windows environment. Can Samba be used to access iw-home config files from a windows client. I did not find detail in the doc on the iw-home permissions or accessing config files through samba.

iwts is the user which owns the TS server process in 6.7.1
Does your Solaris 10 system use Kerberos authentication? If so, there are some contortions I believe you have to go through to prevent samba from overwriting the the kerberos keytabs (or something like that). The Unix admin where I'm working just went through this (and got it resolved with help from the Windows admins) - but I don't (yet) have details about what was done (sorry).
Another thing to check for is the directory access mode bits on the iw-store directories - at my current customer's site, root has a umask that set the directory permissions to drw------- (not lack of execute bit). Running as "iwts" you need to do something like:

sudo find /iw-store -type d | xargs sudo chmod u+x

Hope some of that helps.

Tim__D

iwts is the user which owns the TS server process in 6.7.1
Does your Solaris 10 system use Kerberos authentication? If so, there are some contortions I believe you have to go through to prevent samba from overwriting the the kerberos keytabs (or something like that). The Unix admin where I'm working just went through this (and got it resolved with help from the Windows admins) - but I don't (yet) have details about what was done (sorry).
Another thing to check for is the directory access mode bits on the iw-store directories - at my current customer's site, root has a umask that set the directory permissions to drw------- (not lack of execute bit). Running as "iwts" you need to do something like:
sudo find /iw-store -type d | xargs sudo chmod u+x
Hope some of that helps.

So using Samba to allow for easy access to iw-home and other Teamsite config files is possible? Have you seen this at many of your sites?

Most of the files I have seen so far are either owned by root or iwts. I was hoping that a small and restricted admin group could be created on the UNIX machine which could provide access to some files and direcories like iw-home/iw-perl, iw-home, etc... but I dont want to change the permissions in a way that would negativly impact the product.

Adam Stoller

So using Samba to allow for easy access to iw-home and other Teamsite config files is possible? Have you seen this at many of your sites?

Most of the files I have seen so far are either owned by root or iwts. I was hoping that a small and restricted admin group could be created on the UNIX machine which could provide access to some files and direcories like iw-home/iw-perl, iw-home, etc... but I dont want to change the permissions in a way that would negativly impact the product.

iw-home is not, by default, a shared location. So you would need to share it (NFS / Unix side) in order to be able to mount it through samba to the PC.

I believe "iwts" is both a userid and a groupid - as such you could probably add other people to the "iwts" group to give them access to some of the files and directories. The big thing to be careful about is to not muck with files that have the setuid / setgid bits set - most other files can have the group-owner and group-access bits changed without affecting the product.