Instead of dropping this bug report with won'tfix after 8 years it would have
been appropriate to reassign it to the useradd package immediately.
Thanx very much for your help
Harri
Control: tags -1 wontfix
thanks
On Mon, Dec 16, 2013 at 04:13:26PM +0100, Harald Dunkel wrote:
> - I agree that nsswitch.conf is of no help here. The suggestion of
> this bug report is to ignore remote directory services. Obviously
> this implies to bypass nsswitch.conf and to read
Please note
- I don't run adduser --system, but some postinst scripts do. Looking
at the official interface to manage packages I am not even supposed
to know which system user accounts are created. All I see is that
some unrelated system services are not started at boot time, if the
On 11/21/13 20:40, Stephen Gran wrote:
adduser uses the system nss routines. It's up to the admin of the
system to set them up appropriately, sorry.
nsswitch.conf does not provide an interface to
introduce new group IDs. getent uses nss, but this
is a bug report about adduser.
Regards
This one time, at band camp, Harald Dunkel said:
On 11/21/13 20:40, Stephen Gran wrote:
adduser uses the system nss routines. It's up to the admin of the
system to set them up appropriately, sorry.
nsswitch.conf does not provide an interface to introduce new group
IDs. getent uses
This one time, at band camp, Harald Dunkel said:
Problem:
adduser --system or addgroup --system refuse to proceed
if the name is already provided by a remote directory
service for passwd or group. On the next reboot the user
or group names cannot be resolved, if the (unrelated!)
directory
Package: adduser
Version: 3.113+nmu3
Problem:
adduser --system or addgroup --system refuse to proceed
if the name is already provided by a remote directory
service for passwd or group. On the next reboot the user
or group names cannot be resolved, if the (unrelated!)
directory service is not
7 matches
Mail list logo
