From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
if I use redhat-config-users the homedirectory wasn't created.
I doesn't do something other then on ix86. The RPM seems not been
created/compiled for S390 (noarch).
Because off that no error is displayed and it is a binary, I'm not
able to say what's going wrong.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.create a new user
3.check "create homedir"
Actual Results: user was created
/home is empty
Expected Results: user and homedirectory should been created after
hiting the "Ok"-button
every input would show the same
Just checking whether I get this correctly: You are trying to add a
user on an s390 box (31 or 64 bits?) and it fails to create the home
As you noticed, the package is noarch because it doesn't contain
architecture specific stuff. The binary you are referring to is
probably /usr/bin/consolehelper (/usr/bin/redhat-config-users is just
a symlink to it) which is used to let ordinary users run the tool,
then ask for the root password and then run the real tool which is
/usr/share/redhat-config-users/redhat-config-users and everything else
in the same directory. If you want to take a look, please do there ;-).
Just for the record: I tried to reproduce this on x86, but it works as
expected (creates the user's homedir).
Sorry an Isue with Lotus Notes on RedHat for zSeries does take my time
so I couldn't test until now. Al i got from my user was that he not us
"/home/<uerid>" because it should be an user for a deamon who should
have his homedir linked to the applikationdirektory, sorry for the
Now I tested a little bit and all I got was:
libuser fatal error: lu_homedir_populate() called with non-NULL
*error/usr/share/redhat-config-users/redhat-config-users: line 4:
29068 Aborted /usr/bin/python2.2
So it should be a problem in redhat-config-users, isn't it???
This rather seems like a problem in the underlying libuser package. Which
version of that one do you have?
This should be fixed in the upcoming RHEL 3 update 4.
*** This bug has been marked as a duplicate of 135625 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.