On Wed, 10 Feb 1999, Jacques Gelinas wrote:
> On Wed, 10 Feb 1999, Neil Zanella wrote:
> > Hello,
> > I am running Linuxconf 1.12r5 ...
> > There seems to be a problem with Linuxconf on my Red Hat 5.2 system:
> > When I try to disactivate a user account nothing happens. Here is what
> > is reported in /var/log/messages when I try to disable the account
> > named "guest". It seems linuxconf thinks I'm trying to change shells instead.
> >
> > Feb 9 23:25:28 river usermod[5047]: change user `guest' shell from
> > `/bin/bash' to `/bin/bash'
>
> Linuxconf blindly call usermod after a change to an account even if that
> yield no change (could be smarter). The problem you have is that disabling
> an account does not work unless you use shadow password, which is a good
> idea anyway. To activate shadow password, just do
>
> /usr/sbin/pwconv
Well, shouldn't linuxconf at least pop up a warning saying:
"failed: shadow password not enabled"
or something like that. After all, linuxconf is meant to be user friendly.
Plus, can't Linuxconf just proceed as follows? :
1) Check whether shadow password is enabled or not
2) If not enabled put an asterisk at the beginning of the password field
in /etc/passwd
3) Otherwise procede as usual.
I think this would be a smart way for Linuxconf to operate.
Do we need a patch for this?
> and then you will be able to disable accounts and do much more. The user
> account dialog will be enlarge with new fields.
Thanks. I hope that non shadow password accounts will eventualy be supported.
...
I would like to thank all linuxconf developers for creating linuxconf.
Neil Zanella
[EMAIL PROTECTED]
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
