Re: adding users in RaQ


Subject: Re: adding users in RaQ
From: Jim Dory (jdory@gci.net)
Date: Fri Apr 26 2002 - 18:06:48 AKDT


Fielder George Dowding wrote:

>On Fri, 26 Apr 2002 12:00:42 -0700
>Jim Dory <jdory@gci.net> wrote:
>
>>I've found an adduser, useradd and groupadd in usr/sbin.
>>
>
>These commands are for UNIX users and groups. Samba users and groups
>are on a different planet.
>

Well, for better or worse I was playing around with instructions to
create a primary domain controller based on a tutorial I found here:
http://www-1.ibm.com/servers/esdd/tutorials/samba.html?t=gr,l=335,p=SambaTutorial
(it requires a name/email registration, but I doubt you have to put in a
real one if so inclined)

Part of the instructions were for adding groups:

[root@phoenix root]# group -g 200 admins
[root@phoenix root]# group -g 201 machines

and then:

"As noted, Samba will not allow you to add an entry to the smbpasswd
file (user or
machine) unless there is a existing UNIX account for that user. So the
first step is to
create an entry for the client in /etc/passwd:

[root@phoenix root]# /usr/sbin/useradd -g machines -d /dev/null -c
"machine id" -s

*/bin/false /machine_name$/*

[root@phoenix root]# passwd -l machine_name$
Changing password for user machine_name$
Locking password for user machine_name$
"
Then it goes on to adding smbpasswd stuff..

So hence, you can see that group and useradd were pretty important for
me to follow the instructions.

Luckily the commands started working. Now I just have to figure out how
to get the 'list of servers not found" to go away after clicking on the
workgroup under network neighborhood. Something to do with netlogon for
W2k and host files.. which I'm researching and trying to learn. I edited
the ect/hosts file and created a lmhosts file in the linux box but
better go back and look at em. But I think I need to do something
similar in the windows boxes. Sheesh, feel like a dolt.

>
>Right! A practice to be avoided. Each system seems to have its own
>peculiarities, so I use the command line utilities instead of diving
>into the files to muck around with vi or whatever your favorite
>text/programmer's editor might be.
>

So I haven't played around with vi yet, but have been using pico. I read
somewhere that you should use the -w parameter to avoid wrapping stuff
in the files.. I assume you should use that all the time with config
files? People seem to favor vi so maybe I'll find some time to try it out.

Thanks for the rest of the info too.. appreciate it!

Cheers, JD

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.



This archive was generated by hypermail 2a23 : Fri Apr 26 2002 - 18:08:06 AKDT