User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
Tim David wrote:
No, but I did ask that. In fact, all of us changed our passwords today
to make sure.
The reboot fix is what puzzles me now. After a reboot, everything went
back to normal. That tells me that it wasn't an error on some admins
part. (which I looked heavily into yesterday and last night) If
something like that was wrong, the reboot would not have fixed it.
Well, reboots heal all sorts of things --- the problem is what caused
the failure before. It could be in the auth routines that samba called
rather samba itself.
I tried looking up the log mssages you posted in the Linux sources.
Samba errors show the source file and line number that generate it.
>>> [2004/10/27 16:26:13, 0]
>>> /SourceCache/samba/samba-56/samba/source/lib/substitute.c:
>>> alloc_sub_basic(500)
>>> alloc_sub_basic: NULL source string! This should not happen
This is in a routine doing string substitions in SMB names and
it was passed an empty string as input. This is the routine
that handles things like %N, %U, etc. in smb.conf file. This
could indicate a problem there or a corruption of the in-memory
copy.
>>> [2004/10/27 16:34:52, 0]
>>> /SourceCache/samba/samba-56/samba/source/smbd/service.c:
>>> set_admin_user(321)
>>> test1 logged in as admin user (root privileges)
I couldn't find this in the Linux sources for smbd/service.c which
indicates this might be code that Apple added. I believe the
OS-X sources are available somewhere.
>
My concern is that if Samba breaks, I would hope it would remove all
access as opposed to granting full access to everyone. It seems like a
strange default behavior. What's scarier is that I'll never know when
it breaks because nobody will call with trouble accessing files. I'll
have to test it constantly now.
I couldn't find mention of this on the Samba archives so it sounds
pretty rare.
I had my logs turned up pretty high because it's a new server. The bad
part about that is it's hard to week through all of this to find out if
anything specific happened or if Samba just choked.
Just remember that Apple's idea of HIGH is 2. Samba has levels up
to 10 and it's also capable of logging with different files and/or levels
for each client machine. Furthermore logging levels can be changed dynamically
using the smbcontrol utility.
This is not to say that it would be easy to track down, just that
you have many ways to tailor or turn logging way up if this happens
again
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
