Smc and smuser both put wrong home directory in /etc/passwd

Question

Hello,
I'm trying to use 'smuser add' as an alternative to 'useradd' in a setuid script, using -d to specify a home directory other than the default. Unfortunately, although the directory is created in the right place, the default is written into /etc/passwd.
%smuser add -u sapadm -p ***** -- -d /appuser/inputs/tom -g sapusers -n tom -s /bin/sh
Loading Tool: com.sun.admin.usermgr.cli.user.UserMgrCli from localhost
Login to localhost as user sapadm was successful.
Download of com.sun.admin.usermgr.cli.user.UserMgrCli from localhost was successful.
% ls -al /appuser/inputs/tom
total 14
drwxr-x--- 2 tom sapusers 5 Mar 28 15:48 .
drwxr-xr-x 3 sj staff 3 Mar 28 15:48 ..
-rw-r--r-- 1 tom sapusers 136 Mar 28 15:48 .cshrc
-rw-r--r-- 1 tom sapusers 157 Mar 28 15:48 .login
-rw-r--r-- 1 tom sapusers 174 Mar 28 15:48 .profile
% cat /etc/passwd
tom:x:101:1002::/home/tom:/bin/sh
% ls -al /home/tom
/home/tom: No such file or directory
% uname -a
SunOS sun03 5.10 Generic_127112-07 i86pc i386 i86pc
Exactly the same thing happens when I use the SMC2.1 GUI - even though it echoes back to me that the directory path qill /appuser/inputs before I hit 'finish', the directory is created correctly, but /home/tom goes into /etc/passwd.
Is there any fix/workaround for this, or am I back to an old-fashioned useradd in a setuid script?
Thanks
-- Steve

Answer 1

Father wrote:
that way, they are chrooted into an empty directory and have no files they can tamper with
isnt that a little dangerous??
What files a user can change is determined by the files' permission settings, not by the user's homedir. The homedir only tells what the initial working directory when a user logs in is, nothing else, it doesn't implicit writing or even reading access. So no, it's not dangerous, not even a little.