[KLUG Members] Help for upgrade to Samba 3.0.1 (LDAPSAM) fm 2.2.8a anybody?

[Jim C.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adam Williams wrote:
|>| It might not be bad to walk away and do something else for a day and go
...

|>~  No such user Administrator [J9STARR] - using guest account
| What does "id Administrator" return if you run it on the PDC?

[root@enigma root]# id Administrator
uid=998(Administrator) gid=512(Domain Admins) groups=512(Domain Admins)


|>and also there was this in another window:
|>[root@enigma samba3]# tail -f /var/log/samba3/log.kaliklak | grep root
...

|>Huh? "(uid=root)(objectclass=sambaSamAccount))"? Why is it looking for
that?
| Well, you mapped Administrator to root, yes?

Right but that was a root group not a root user.  I assume that
sambaSamAccount means that it is looking for an actual user named root.

I do have this setting:

[root@enigma samba3]# cat smbusers
# Unix_name = SMB_name1 SMB_name2 ...
root = Administrator admin
nobody = guest pcguest smbguest


|>and also:
|>[root@enigma samba3]# tail -f /var/log/samba3/log.kaliklak | grep J9STARR
...
|>NOTE: Kaliklak is the name of the client and Enigma is the server.
|>J9STARR is the domain.
|
|
| What does "ldapsearch uid=root" return?

[root@enigma root]# ldapsearch uid=root
ldap_sasl_interactive_bind_s: No such object

|>I've noticed that despite the change in max log size I made that the
|>file stays right at 5K.  I was trying to expand it so that I could get
|>more data but I can't seem to.  As it is, so much data wizes by that I
|>can't hang on to it.  To mark a starting point I tried this:
|>echo "JIMS MARKER" >> /var/log/samba3/log.kaliklak
|>But then couldn't find the text marker:
|>[root@enigma samba3]# grep "JIMS MARKER" *
|>[root@enigma samba3]#
|
|
| It probably gets rotated away.
|
| You log file directive looks like?
| log file = /var/log/samba/log.%m

Yup. Suppose I don't actually need the include line mentioned eariler,
except for the debug level. Thing is that I can't seem to get the
log/debug level to back off at all from 10 anyway. Hmmm, perhaps if it
encounters a loglevel or debug level that is higher it defaults to the
high one.  I'll try a global reduction in level and see if I can't get
something more manageable. Still seems like I am getting bloody well
everything.

| I just don't specify a max size, it seems to work.
|
| And you have something like -
|    logon script = %G.bat
|    logon path = \\BARBEL\PROFILES\%U
|    logon drive = f:
|    logon home = \\SARDINE\HOMEDIR
| - in smb.conf to cover for the possibility that an attribute isn't
| specified in LDAP?

No specs for this.  Wanted the defaults, i.e. profiles that live in
users /home directories etc. I have no use for a logon script that I
know of either and users are added with logon path, drive and home set
to a default value.

There could be permissions problems with the underlying filesystem as
I've just managed to fix the write access to my public share by
changeing these.  I don't see how this would affect the ability to join
a domain though and we already know that it is probably some kind of
mapping issue anyway.

- --

- -----------------------------------------------------------------
| I can be reached on the following messenger services:		|
|---------------------------------------------------------------|
| MSN: j_c_llings@hotmail.com  AIM: WyteLi0n  ICQ: 123291844 	|
|---------------------------------------------------------------|
| Y!: j_c_llings               Jabber: jcllings@nureality.com	|
- -----------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAEDz457L0B7uXm9oRAkdxAJ9RdtSiFbDv/IiD6VJ2ywrSsO7k+wCfeoeN
lrcmfouUFbH35y20EE/TDsM=
=HY8s
-----END PGP SIGNATURE-----