[Samba] smbumount will not let me unmount
The smbumount manual says: With this program, normal users can unmount smb-filesystems, provided that it is suid root. smbumount has been written to give normal Linux users more control over their resources. I installed it as setuid root: -rwsr-xr-x1 root root 618675 Apr 7 23:11 /usr/bin/smbumount Then I use smbmount to mount a share: smbmount //server/share ~/mntpoint rw And it works fine. But when I want to unmount it as a user: smbumount ~/mntpoint I get this error: You are not allowed to umount /home/nir/mntpoint So what is the (mount) point in this? what am I doing wrong? btw - I also installed smbmnt as setuid root - otherwise it will not let me mount at all as a regular user. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
sesssetup.c, encrypted passwords and unicode
Hi there! I've been trying to get Samba 3.0 to use plaintext passwords and unicode for
a while now.
The first thing I stumbled on was solved, it was a service pack that needed to be
applied to w2k. (Thanks!)
This is the second thing I stumbled on:
In line 613 of sesssetup.c (latest CVS) there is the following code snippet:
} else {
pstring pass;
srvstr_pull(inbuf, pass, smb_buf(inbuf),
sizeof(pass), passlen1, STR_TERMINATE);
plaintext_password = data_blob(pass, strlen(pass)+1);
}
From what (limited) understanding I have, passlen1 in this case is the non-unicode
password, and passlen2 is the unicode password. The code pull the wrong passlen, and
consequently the wrong password was checked against the database. ( a password with a
length of 0)
Changing the code to use passlen2 basically allowed me to login, but I'm pretty sure
this is not the correct fix (I would think that one should first check if the
connection is unicode or not).
Just FYI,
Thanks :)
Nir.
--
Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org
Father, why are all the children weeping? / They are merely crying son
O, are they merely crying, father? / Yes, true weeping is yet to come
-- Nick Cave and the Bad Seeds, The Weeping Song
RE: rd /s, can't find the file specified (internal reference b1996)
-Original Message- From: Richard Sharpe [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 10:43 AM To: Nir Soffer Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: rd /s, can't find the file specified (internal reference b1996) On Wed, 19 Mar 2003, Nir Soffer wrote: I can't reproduce this at all on a recent (CVS) build of SAMBA_3_0. Can you give me more details on *exactly* how you reproduce it please ? What I did was simply do, on the unix side: mkdir b1996 cd b1996 touch nirtest123456 touch nirtest12345 and on the W2K side use a command line prompt, map the drive using net use, and try to rd /s b1996 OK, that explains the insistence on using short names. Did you use command or cmd? I used cmd. I specified I was using the command line on the beginning, and that everything worked perfectly alright from the explorer and the GUIs. I also thought that the rd /s in the subject was a big hint ;) Is it reproducable on your end too, or is something in my configuration screwy? Nir. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: rd /s, can't find the file specified (internal reference b1996)
-Original Message- From: Richard Sharpe [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 10:43 AM To: Nir Soffer Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: rd /s, can't find the file specified (internal reference b1996) On Wed, 19 Mar 2003, Nir Soffer wrote: I can't reproduce this at all on a recent (CVS) build of SAMBA_3_0. Can you give me more details on *exactly* how you reproduce it please ? What I did was simply do, on the unix side: mkdir b1996 cd b1996 touch nirtest123456 touch nirtest12345 and on the W2K side use a command line prompt, map the drive using net use, and try to rd /s b1996 OK, that explains the insistence on using short names. Did you use command or cmd? Okay. I was being stupid. Very very stupid, and I apologize. Turns out mangled filenames was disabled. But is this the expected error when manged filenames are disabled? Nir. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: rd /s, can't find the file specified (internal reference b1996)
On Mon, 17 Mar 2003, Nir Soffer wrote: Enjoy. OK, now that I have looked at both traces in more detail, here is what is happening: The bad trace, perhaps the one from UNIX, is returning exactly the same short name for each of those files, 0123456789AB. The client tries to use the short name, and the server obviouly gets confused. In the second case, the short names are all correct looking names, or the form 012345~1, 012345~2 etc. Have you modified Samba's name mangling code to do silly things? Not at all. I used straight up vanilla from CVS. I'll take another look at the configuration, maybe I have it configured to stupidity-mode when it comes to mangling, or something... Nir. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: rd /s, can't find the file specified (internal reference b1996)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 4:44 AM To: Nir Soffer Cc: [EMAIL PROTECTED] Subject: Re: rd /s, can't find the file specified (internal reference b1996) On Sun, Mar 16, 2003 at 06:47:44PM +0200, Nir Soffer wrote: Following up to myself, reproducing this is apparently even simpler than I thought - simply do a: touch nir test test and try to delete it from a DOS command line. It will fail. nirtest123456 fails as well, but nirtest12345 so it seems to filename size related. 13 characters won't work and 12 will. Perhaps it's because something is geared towards 8 characters, a dot, and 3 characters somewhere along the line? Needless to say, it works fine on w2k shares... I can't reproduce this at all on a recent (CVS) build of SAMBA_3_0. Can you give me more details on *exactly* how you reproduce it please ? What I did was simply do, on the unix side: mkdir b1996 cd b1996 touch nirtest123456 touch nirtest12345 and on the W2K side use a command line prompt, map the drive using net use, and try to rd /s b1996 That's all I did... I sent traces to the list and rsharpe, and those traces indicate it has something to do with mangling, so I'm going to take a closer look at my configuration and see if I did anything there... Thanks, Nir. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: rd /s, can't find the file specified (internal reference b1996)
Enjoy. From a very very fast look, it looks like something with file mangling, but IANA Samba Expert. baddosdel.cap is against Samba-CVS (From yesterday) gooddosdel.cap is against my personal W2K workstation. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song -Original Message- From: Richard Sharpe [mailto:[EMAIL PROTECTED] Sent: Monday, March 17, 2003 9:23 AM To: Nir Soffer Cc: [EMAIL PROTECTED] Subject: RE: rd /s, can't find the file specified (internal reference b1996) On Sun, 16 Mar 2003, Nir Soffer wrote: Following up to myself, reproducing this is apparently even simpler than I thought - simply do a: touch nir test test and try to delete it from a DOS command line. It will fail. nirtest123456 fails as well, but nirtest12345 so it seems to filename size related. 13 characters won't work and 12 will. Perhaps it's because something is geared towards 8 characters, a dot, and 3 characters somewhere along the line? Needless to say, it works fine on w2k shares... Can you get us a sniff? Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com baddosdel.cap Description: baddosdel.cap gooddosdel.cap Description: gooddosdel.cap
RE: FW: encrypt passwords = no, security=user, samba 3.0a22
Here you go. Enjoy :) N. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song -Original Message- From: Richard Sharpe [mailto:[EMAIL PROTECTED] Sent: Saturday, March 15, 2003 2:30 AM To: Nir Soffer Cc: Christopher R. Hertel; [EMAIL PROTECTED] Subject: RE: FW: encrypt passwords = no, security=user, samba 3.0a22 On Tue, 11 Mar 2003, Nir Soffer wrote: FWIW turning off unicode with unicode=no helps somewhat, and both ethereal and Samba parse the session request correctly: Hmmm, I fixed a problem in Ethereal around Unicode handling last week at Connectathon. I would be very interested in a trace that shows the problem. Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com badpass.cap Description: badpass.cap aftersp.cap Description: aftersp.cap nounicode.cap Description: nounicode.cap
RE: rd /s, can't find the file specified (internal reference b1996)
Following up to myself, reproducing this is apparently even simpler than I thought - simply do a: touch nir test test and try to delete it from a DOS command line. It will fail. nirtest123456 fails as well, but nirtest12345 so it seems to filename size related. 13 characters won't work and 12 will. Perhaps it's because something is geared towards 8 characters, a dot, and 3 characters somewhere along the line? Needless to say, it works fine on w2k shares... Nir. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song -Original Message- From: Nir Soffer Sent: Sunday, March 16, 2003 1:58 PM To: [EMAIL PROTECTED] Subject: rd /s, can't find the file specified (internal reference b1996) Hi! Our QA department stumbled across the following problem: From the W2K commandline rd /s on a large directory reports: The system cannot find the file specified. on a rather large amount of files. I've yet to figure out what the connection between them is, but I'm starting to believe they're files with spaces. I've encountered this problem on Samba v3.0a20, v3.0a22, and latest Samba 3 CVS. I did not encounter this problem on all that variants of Samba v2.2 I've tried (Specifically v2.2.1a, and some more I don't really remember now). I didn't even encounter it on v2.0.7. To reproduce, simply do a: net use * \\server\share D: (or whatever drive you got) mkdir bug cd bug xcopy /e C:\winnt cd .. rd /s bug Apparently del *.* is having problems with these files as well, and regular del Soap Bubbles.bmp also returned with the same error. In case I wasn't clear, this happens only via the command line, and NOT via the Windows Explorer. Deleting from there works just fine. Attached is an l10 log of me trying to delete a file... Anyone have any ideas, or anything he wants me to try? For reference, the internal bug number of this at Exanet is Bug 1996. Thanks, Nir. -- Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
FW: encrypt passwords = no, security=user, samba 3.0a22
Hi again! After quite a lot of help from Christopher Hertel (Thanks, Chris!), I managed W2K to play nicey-nicey with UNICODE and plaintext passwords. It seems everything he said was pure golden truth, as detailed in the following MS KB article: http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B257292 After installing the latest Service Packs on my test machine, apparently the problem went away (at least judging by ethereal and the Samba logs). I still haven't managed to log in properly using non-encrypted passwords, so if I find anything else I'll keep you posted. This one's probably on my side of configuration. :) Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -Original Message- From: Nir Soffer Sent: Tuesday, March 11, 2003 4:30 PM To: '[EMAIL PROTECTED]' Subject: FW: encrypt passwords = no, security=user, samba 3.0a22 Something our QA department stumbled on: I try to log on to my Samba 3.0a22 installation (make, make install, the usual shebang). The client name is CACOMISTLE (not the NativeOS), the user name is nirs, (not the domain). Any ideas or thoughts, or are we doing something incredibly stupid? (I've been reading some stuff about not having a guest user in the passdb causing such errors, but I do have a nobody user in the password files. Shouldn't this work properly out of the box? There's a log snippet that shows this may be related..) Thanks, Nir. Log snippets: [2003/03/11 16:21:40, 5] auth/auth_util.c:debug_unix_user_token(530) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups [2003/03/11 16:21:40, 5] smbd/uid.c:change_to_root_user(217) change_to_root_user: now uid=(0,0) gid=(0,0) [2003/03/11 16:21:40, 4] smbd/reply.c:reply_tcon_and_X(255) Got device type ? [2003/03/11 16:21:40, 5] smbd/service.c:make_connection(843) making a connection to 'normal' service ipc$ [2003/03/11 16:21:40, 5] lib/username.c:Get_Pwnam(288) Finding user nobody [2003/03/11 16:21:40, 5] lib/username.c:Get_Pwnam_internals(223) Trying _Get_Pwnam(), username as lowercase is nobody [2003/03/11 16:21:40, 5] lib/username.c:Get_Pwnam_internals(251) Get_Pwnam_internals did find user [nobody]! [2003/03/11 16:21:40, 3] smbd/service.c:make_connection_snum(525) Connect path is '/tmp' for service [IPC$] [2003/03/11 16:21:38, 3] smbd/sec_ctx.c:set_sec_ctx(287) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2003/03/11 16:21:38, 5] auth/auth_util.c:debug_nt_user_token(511) NT user token: (NULL) [2003/03/11 16:21:38, 5] auth/auth_util.c:debug_unix_user_token(530) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups [2003/03/11 16:21:38, 5] smbd/uid.c:change_to_root_user(217) change_to_root_user: now uid=(0,0) gid=(0,0) [2003/03/11 16:21:38, 3] smbd/sesssetup.c:reply_sesssetup_and_X(482) wct=13 flg2=0xc807 [2003/03/11 16:21:38, 3] smbd/sesssetup.c:reply_sesssetup_and_X(582) Domain=[nirs] NativeOS=[CACOMISTLE] NativeLanMan=[Windows 2000 2195] ^^^ [2003/03/11 16:21:38, 3] smbd/sesssetup.c:reply_sesssetup_and_X(601) sesssetupX:[EMAIL PROTECTED] [2003/03/11 16:21:38, 6] param/loadparm.c:lp_file_list_changed(2347) lp_file_list_changed() file /usr/local/samba/lib/smb.conf - /usr/local/samba/lib/smb.conf last mod_ time: Tue Mar 11 16:16:23 2003 smb.conf: [global] blocking locks = no dns proxy = no encrypt passwords = no keepalive = 120 level2 oplocks = no lock directory = /usr/local/samba/var/locks locking = no log file = /tmp/log.smbd.%m log level = 10 machine password timeout = 9 mangled names = no map to guest = bad user name resolve order = lmhosts wins bcast host netbios name = windlg1 oplocks = no security = user socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash workgroup = exanet-qa winbind enum groups = yes winbind enum users = yes winbind gid = 1-2 winbind separator = + winbind uid = 1-2 [CIFS] comment = cifs exported dir path = /mnt/fs read only = no -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
FW: encrypt passwords = no, security=user, samba 3.0a22
Something our QA department stumbled on: I try to log on to my Samba 3.0a22 installation (make, make install, the usual shebang). The client name is CACOMISTLE (not the NativeOS), the user name is nirs, (not the domain). Any ideas or thoughts, or are we doing something incredibly stupid? (I've been reading some stuff about not having a guest user in the passdb causing such errors, but I do have a nobody user in the password files. Shouldn't this work properly out of the box? There's a log snippet that shows this may be related..) Thanks, Nir. Log snippets: [2003/03/11 16:21:40, 5] auth/auth_util.c:debug_unix_user_token(530) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups [2003/03/11 16:21:40, 5] smbd/uid.c:change_to_root_user(217) change_to_root_user: now uid=(0,0) gid=(0,0) [2003/03/11 16:21:40, 4] smbd/reply.c:reply_tcon_and_X(255) Got device type ? [2003/03/11 16:21:40, 5] smbd/service.c:make_connection(843) making a connection to 'normal' service ipc$ [2003/03/11 16:21:40, 5] lib/username.c:Get_Pwnam(288) Finding user nobody [2003/03/11 16:21:40, 5] lib/username.c:Get_Pwnam_internals(223) Trying _Get_Pwnam(), username as lowercase is nobody [2003/03/11 16:21:40, 5] lib/username.c:Get_Pwnam_internals(251) Get_Pwnam_internals did find user [nobody]! [2003/03/11 16:21:40, 3] smbd/service.c:make_connection_snum(525) Connect path is '/tmp' for service [IPC$] [2003/03/11 16:21:38, 3] smbd/sec_ctx.c:set_sec_ctx(287) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2003/03/11 16:21:38, 5] auth/auth_util.c:debug_nt_user_token(511) NT user token: (NULL) [2003/03/11 16:21:38, 5] auth/auth_util.c:debug_unix_user_token(530) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups [2003/03/11 16:21:38, 5] smbd/uid.c:change_to_root_user(217) change_to_root_user: now uid=(0,0) gid=(0,0) [2003/03/11 16:21:38, 3] smbd/sesssetup.c:reply_sesssetup_and_X(482) wct=13 flg2=0xc807 [2003/03/11 16:21:38, 3] smbd/sesssetup.c:reply_sesssetup_and_X(582) Domain=[nirs] NativeOS=[CACOMISTLE] NativeLanMan=[Windows 2000 2195] ^^^ [2003/03/11 16:21:38, 3] smbd/sesssetup.c:reply_sesssetup_and_X(601) sesssetupX:[EMAIL PROTECTED] [2003/03/11 16:21:38, 6] param/loadparm.c:lp_file_list_changed(2347) lp_file_list_changed() file /usr/local/samba/lib/smb.conf - /usr/local/samba/lib/smb.conf last mod_ time: Tue Mar 11 16:16:23 2003 smb.conf: [global] blocking locks = no dns proxy = no encrypt passwords = no keepalive = 120 level2 oplocks = no lock directory = /usr/local/samba/var/locks locking = no log file = /tmp/log.smbd.%m log level = 10 machine password timeout = 9 mangled names = no map to guest = bad user name resolve order = lmhosts wins bcast host netbios name = windlg1 oplocks = no security = user socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash workgroup = exanet-qa winbind enum groups = yes winbind enum users = yes winbind gid = 1-2 winbind separator = + winbind uid = 1-2 [CIFS] comment = cifs exported dir path = /mnt/fs read only = no -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
RE: FW: encrypt passwords = no, security=user, samba 3.0a22
Nir Soffer wrote: Something our QA department stumbled on: I try to log on to my Samba 3.0a22 installation (make, make install, the usual shebang). The client name is CACOMISTLE (not the NativeOS), the user name is nirs, (not the domain). Any ideas or thoughts, or are we doing something incredibly stupid? At a guess, you are using plaintext passwords with Unicode. If my guess is correct (a simple capture of the SMB SESSION SETUP ANDX exchange would prove it) then read on... I do not know how to convince a Windows *server* to request plaintext passwords. As you are probably aware, it is easy to get Samba to request plaintext if that's really what you want to do. What that means is that the combination of Unicode and plaintext passwords is unusual. I have seen that W2K and W/XP clients will send Unicode plaintext passwords if Samba requests it. Unfortunately, they get the field values wrong--in different ways--and it breaks the existing parsing in Samba. [ snip wonderful explanation ] The Windows systems that I've been able to check do not send Plaintext Unicode passwords correctly. My *guess* is that Microsoft never tested this because their servers don't set up the situation that would require testing. I believe that Samba can compensate, but I have not had time to look at the code (let alone fix it). It should be an easy fix. Eg.: if( Unicode Password begins with 0x00 ) skip a byte if( Unicode Password does not end in 0x ) Add two to the password length before processing Someone care to look into providing a patch? It seems to me that a more correct fix would be, in the case of encrypt passwords = no, to request a normal password and not a UNICODE one. Is this even possible in the protocol? (e.g - request non-unicode passwords, but still support non-unicode filenames?) This is definitely broken now if this the case, regardless where the bug is... Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
RE: FW: encrypt passwords = no, security=user, samba 3.0a22
Nir Soffer wrote: : : It seems to me that a more correct fix would be, in the case of encrypt passwords = no, to request a normal password and not a UNICODE one. Is this even possible in the protocol? (e.g - request non-unicode passwords, but still support non-unicode filenames?) Unicode is either ON or OFF. If Unicode is negotiated, then the Windows clients will try to send a Unicode password. This is definitely broken now if this the case, regardless where the bug is... There are bugs in the Windows clients, clearly, but I think that we can work around them. I also think that smbclient needs to be tested in this regard. FWIW turning off unicode with unicode=no helps somewhat, and both ethereal and Samba parse the session request correctly: [2003/03/11 20:11:30, 3] smbd/sesssetup.c:reply_sesssetup_and_X(732) Domain=[CACOMISTLE] NativeOS=[Windows 2000 2195] NativeLanMan=[Windows 2000 5 .0] [2003/03/11 20:11:30, 3] smbd/sesssetup.c:reply_sesssetup_and_X(742) sesssetupX:[EMAIL PROTECTED] So it seems you hit the mark. Now it's time to figure out how to fix it :) Thanks again! Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
Patches for winbindd over TCP and a failover port option
Our product uses Samba as a component. In our product we were forced to modify certain parts of Samba, namely: Winbindd running over TCP (to a remote host) Smbd listening to an additional failover port. Allow listening on non-broadcast interfaces. All these changes are very minimal. In order to comply with the GPL and provide the community with what little code we've modified, attached is the patch file between this version and Samba 3.0a20. I'm afraid we've never merged it with later versions, since they never seemed to work. I sincerely hope this helps people, Regards, Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
REPOST: Patches for winbindd over TCP and a failover port option
)); /* * Setting is_daemon here prevents us from eventually calling -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -Original Message- From: Neil Hoggarth [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 18, 2003 6:26 PM To: Nir Soffer Cc: Guenther Deschner; Subject: Re: Patches for winbindd over TCP and a failover port option On Tue, 18 Feb 2003, Guenther Deschner wrote: you have forgotten to add that patchfile :) Note that since last month the Samba listserver has started filtering message attachments: http://lists.samba.org/pipermail/samba-technical/2003-January/ 041954.html Inline your patches in the message body, or make sure that your mail program flags them as content-type text/plain. Regards, -- Neil Hoggarth Departmental Computer Officer [EMAIL PROTECTED] Laboratory of Physiology http://www.physiol.ox.ac.uk/~njh/ University of Oxford, UK
winbindd losing trust relationship once in a while (Samba 3.0)
Scenario: Fresh compile of Samba 3.0, both a20 and a21. Attempt to use attached smb.conf. EXANET-QA is a part of the EXANET-IL domain (e.g - EXANET-IL is the parent domain). EXANET-QA is supposedly set in compatibility mode. Under certain combinations winbindd seems to be losing it's capability to contact the parent DC. Samba 3.0a20 works, spordically, unless you do some things (wbinfo -m, see below). Samba 3.0a21 doesn't work at all for me. Attached are level 10 logs. On the same matter, is Samba 3.0a22 on it's way out? Could this be already fixed? In the case it isn't obvious - Samba 2.2.x works perfectly in this mode. Samba 3.0a20: * I had some problems when load_interfaces was called twice in some situations, but now I can't seem to reproduce it... * When using wbinfo -m winbindd seems to lose all trust information, see follow sequence: [root@plat1 bin]# !./win ./winbindd -s /cluster/config/samba/smb.conf [root@plat1 bin]# !getent getent passwd | grep nirs nirs:x:5125:625::/users4/nirs:/bin/bash EXANET-IL+nirs:x:10088:10001:Nir Soffer:/home/EXANET-IL/nirs:/bin/false [root@plat1 bin]# ./wbinfo -t checking the trust secret via RPC calls succeeded [root@plat1 bin]# ./wbinfo -m [root@plat1 bin]# !getent getent passwd | grep nirs nirs:x:5125:625::/users4/nirs:/bin/bash [root@plat1 bin]# ./wbinfo -t checking the trust secret via RPC calls succeeded As you can see, EXANET-IL+nirs is no longer there. Attached log is log.winbindd.wbinfo Samba 3.0a21: Doesn't work at all. See log.winbindda21 If there is anything I can do to help, I seem to be able to reproduce this at will. I'll be more than glad to attempt whatever you throw at me. Thanks, Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 log.winbindd.wbinfo.bz2 Description: log.winbindd.wbinfo.bz2 log.winbindda21.bz2 Description: log.winbindda21.bz2 smb.conf Description: smb.conf
RE: winbindd losing trust relationship once in a while (Samba 3.0)
[snip] I wonder whether the trusted domains patch that went by today fixes this as well? Would you mind trying it? Since the patch doesn't apply to a20, and I couldn't be bothered to check why properly - I downloaded the CVS version, for the hell of it. The patch didn't apply to that either, so I did it manually. Both before and after the patch, not only did the trusted domains not work, but I couldn't do a wbinfo -u that worked. This snippet probably explains why: [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:winbind_client_read(414) client_read: read 1312 bytes. Need 0 more for a full request. [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:process_request(297) process_request: request fn LIST_USERS [2003/02/12 15:14:42, 3] nsswitch/winbindd_user.c:winbindd_list_users(533) [21233]: list users [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:client_write(460) client_write: wrote 1300 bytes. [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:winbind_client_read(414) client_read: read 0 bytes. Need 1312 more for a full request. [2003/02/12 15:14:42, 5] nsswitch/winbindd.c:winbind_client_read(419) read failed on sock 12, pid 21233: EOF So, sorry, but that doesn't seem to work. Alpha 20 was the last version that actually worked for me... -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
RE: winbindd losing trust relationship once in a while (Samba 3.0)
-Original Message- From: Ken Cross [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 3:41 PM To: Nir Soffer; 'Tim Potter'; [EMAIL PROTECTED] Subject: RE: winbindd losing trust relationship once in a while (Samba 3.0) The patch works on SAMBA_3_0 as of 5 minutes ago. How did you patch it manually? Well, I looked at the patch saw that it moves the static variable last_scan outside of the function and inserted the last_scan = 0 wherever it should be. The messages you see below are normal and don't indicate any real problems. Except the fact that wbinfo -u didn't work. Downloading the CVS again, this is what I got when I ran wbinfo -u (without any patch) 2003/02/12 18:15:37, 6] rpc_parse/parse_prs.c:prs_debug(81) 18 smb_io_pol_hnd domain_pol [2003/02/12 18:15:37, 5] rpc_parse/parse_prs.c:prs_uint32(592) 0018 data1: [2003/02/12 18:15:37, 5] rpc_parse/parse_prs.c:prs_uint32(592) 001c data2: [2003/02/12 18:15:37, 5] rpc_parse/parse_prs.c:prs_uint16(563) 0020 data3: [2003/02/12 18:15:37, 5] rpc_parse/parse_prs.c:prs_uint16(563) 0022 data4: [2003/02/12 18:15:37, 5] rpc_parse/parse_prs.c:prs_uint8s(679) 0024 data5: 00 00 00 00 00 00 00 00 [2003/02/12 18:15:37, 5] rpc_parse/parse_prs.c:prs_ntstatus(621) 002c status: NT_STATUS_INVALID_PARAMETER [2003/02/12 18:15:37, 10] nsswitch/winbindd.c:client_write(460) client_write: wrote 1300 bytes. [2003/02/12 18:15:37, 10] nsswitch/winbindd.c:winbind_client_read(414) client_read: read 0 bytes. Need 1312 more for a full request. [2003/02/12 18:15:37, 5] nsswitch/winbindd.c:winbind_client_read(419) read failed on sock 12, pid 6200: EOF Ken -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] amba.org] On Behalf Of Nir Soffer Sent: Wednesday, February 12, 2003 8:15 AM To: Tim Potter; [EMAIL PROTECTED] Subject: RE: winbindd losing trust relationship once in a while (Samba 3.0) [snip] I wonder whether the trusted domains patch that went by today fixes this as well? Would you mind trying it? Since the patch doesn't apply to a20, and I couldn't be bothered to check why properly - I downloaded the CVS version, for the hell of it. The patch didn't apply to that either, so I did it manually. Both before and after the patch, not only did the trusted domains not work, but I couldn't do a wbinfo -u that worked. This snippet probably explains why: [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:winbind_client_read(414) client_read: read 1312 bytes. Need 0 more for a full request. [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:process_request(297) process_request: request fn LIST_USERS [2003/02/12 15:14:42, 3] nsswitch/winbindd_user.c:winbindd_list_users(533) [21233]: list users [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:client_write(460) client_write: wrote 1300 bytes. [2003/02/12 15:14:42, 10] nsswitch/winbindd.c:winbind_client_read(414) client_read: read 0 bytes. Need 1312 more for a full request. [2003/02/12 15:14:42, 5] nsswitch/winbindd.c:winbind_client_read(419) read failed on sock 12, pid 21233: EOF So, sorry, but that doesn't seem to work. Alpha 20 was the last version that actually worked for me... -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
RE: [Samba] Which .tdb files are safe to remove?
-Original Message- From: Gerald (Jerry) Carter [mailto:[EMAIL PROTECTED]] Sent: Monday, February 10, 2003 7:49 PM To: Peter Sch?ller Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Which .tdb files are safe to remove? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 9 Feb 2003, Peter Schüller wrote: Hello, which .tdb files in /var/lib/samba are safe to remove (rebuilt automatically)? This is for Samba 2.2: * nt*.tdb. * winbindd_idmap.tdb * share_info.tdb I thinks that's it. I wouldn't remove the idmap if any users had files on the server. Their UIDs may get mixed up. Last I looked the idmap _was_ rebuilt, but on-the-fly on a first-come-first-served basis. In several times I removed it all the permissions were mixed-up after winbind ran again. N. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Trusted domains with Samba 3.0alpha21?
On Fri, 2002-11-29 at 03:29, Nir Soffer wrote: Hi there! I appear to be having problems with trusted domains using 3.0a21. Using Samba as a member server, as user nirs on domain Exanet-il I am unable to log on to a member server (snow) who is a member of the Exanet-qa domain. The exanet-qa is supposed to trust exanet-il, and it all worked with 2.2 . This is the relevant log snippet I can find: [2002/11/28 18:26:05, 0] auth/auth_domain.c:domain_client_validate(425) domain_client_validate: unable to validate password for user nirs in domain EX ANET-QA to Domain controller \\KENGURO. Error was NT_STATUS_NO_SUCH_USER. [2002/11/28 18:26:05, 2] auth/auth.c:check_ntlm_password(271) check_password: Authentication for user [nirs] - [nirs] FAILED with error NT _STATUS_NO_SUCH_USER [2002/11/28 18:26:05, 3] smbd/sesssetup.c:do_map_to_guest(38) No such user nirs [EXANET-IL] - using guest account [2002/11/28 18:26:05, 3] smbd/sec_ctx.c:push_sec_ctx(255) Anyone have any idea? Is this supposed to work in 3.0 now? That error is returned by the remote server. The event log on both DCs might be useful. I only have access to the first PDC in the line, and it shows nothing I can spot of any value. Any hints and tips on what exactly I should be looking for? I'd like to stress that the behaviour differs for 2.2.5 which I had installed previously. (Also - another behaviour change I noticed, and please tell me if I'm wrong, is that once if the trust relationship was not established properly, I'll log on as a guest, and now I can a Can't get domain info error. I'm assuming this came with the new NT status codes and is correct behaviour, I'm just wondering if this should be documented somewhere to avoid confusion) Thanks, Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trusted domains with Samba 3.0alpha21?
Hi there! I appear to be having problems with trusted domains using 3.0a21. Using Samba as a member server, as user nirs on domain Exanet-il I am unable to log on to a member server (snow) who is a member of the Exanet-qa domain. The exanet-qa is supposed to trust exanet-il, and it all worked with 2.2 . This is the relevant log snippet I can find: [2002/11/28 18:26:05, 0] auth/auth_domain.c:domain_client_validate(425) domain_client_validate: unable to validate password for user nirs in domain EX ANET-QA to Domain controller \\KENGURO. Error was NT_STATUS_NO_SUCH_USER. [2002/11/28 18:26:05, 2] auth/auth.c:check_ntlm_password(271) check_password: Authentication for user [nirs] - [nirs] FAILED with error NT _STATUS_NO_SUCH_USER [2002/11/28 18:26:05, 3] smbd/sesssetup.c:do_map_to_guest(38) No such user nirs [EXANET-IL] - using guest account [2002/11/28 18:26:05, 3] smbd/sec_ctx.c:push_sec_ctx(255) Anyone have any idea? Is this supposed to work in 3.0 now? thanks, Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] RE: Error code 0
The [EMAIL PROTECTED] list is for user discussions and help. The [EMAIL PROTECTED] is for developer discussions. It is rare and unusual for a message to be appropriate for both lists. Please, folks, don't cross-post unless it's really the right thing to do. For error code listings, see the nterr.h and/or doserr.h files in samba/source/include/. You can also look at: http://msdn.microsoft.com/library/en-us/debug/base/system_erro r_codes.asp?frame=false Err. AFAIK, error code 0 means Success, in nearly every errno system I've seen, btw. I've seen an error code 0 once in Samba, and I was told it has to do with the peer going away. Since the packet doesn't exist or is all zeroed out in these cases, extraction of the error code field in the packet results in a 0. This is what gets reported to the end user. Am I right? Finally, when posting a request for help to the [EMAIL PROTECTED] mailing list, please include all relevant information, including the version of Samba, and the OS type and version of both client and server. Without context, no one can help you. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: Error code 0
The [EMAIL PROTECTED] list is for user discussions and help. The [EMAIL PROTECTED] is for developer discussions. It is rare and unusual for a message to be appropriate for both lists. Please, folks, don't cross-post unless it's really the right thing to do. For error code listings, see the nterr.h and/or doserr.h files in samba/source/include/. You can also look at: http://msdn.microsoft.com/library/en-us/debug/base/system_erro r_codes.asp?frame=false Err. AFAIK, error code 0 means Success, in nearly every errno system I've seen, btw. I've seen an error code 0 once in Samba, and I was told it has to do with the peer going away. Since the packet doesn't exist or is all zeroed out in these cases, extraction of the error code field in the packet results in a 0. This is what gets reported to the end user. Am I right? Finally, when posting a request for help to the [EMAIL PROTECTED] mailing list, please include all relevant information, including the version of Samba, and the OS type and version of both client and server. Without context, no one can help you. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- The poor little kittens; They lost their mittens; And now you all must die. Mew, Mew, Mew, Mew, And now you all must die. www.sluggy.com, 24/10/02
RE: [Samba] Strange filenames after copy to smb-share
-Original Message-
From: mesiol [mailto:mesiol;yourwap.com]
Sent: Wednesday, October 23, 2002 12:32 PM
To: Samba Mailinglist
Subject: [Samba] Strange filenames after copy to smb-share
Hye,
we use a samba 2.2.3a which works fine most time.
now i found that one client has some strange problems.
when the user copies files to the smb-share some of them will
be created
with very strange filenames.
For example let's say the original file is named:
my_nicetestfile.txt then on the server the file will be created as
my_nic~1.txt and also a file will be created called
my_nicefile:{some_strange_chars_here_in}.txt
has someone an idea how to solve this behaviour?
I'm betting on the ADS bug.
It was fixed AFAIK in 2.2.4. I would upgrade to 2.2.6.
Nir.
--
Nir Soffer -=- Software Engineer, Exanet Inc. -=-
10%? What's Bun-bun going to do at the party?
Not hurt me.
http://www.sluggy.com, 6 Oct 2002
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
RE: Samba 2.2.6 rc2 released
Hi! [snip] Changes since 2.2.6pre2 [snip] 17) Merge winbindd with current (more advanced) state of play in APPLIANCE_HEAD Can anyone enlighten to me as to what exactly that means? What functionality was added, what fixes were applied, etc.? Thanks, Nir -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- 10%? What's Bun-bun going to do at the party? Not hurt me. http://www.sluggy.com, 6 Oct 2002
RE: Weekly machine password changes (RE: RE: [Samba] odd: everything SHOULD work... winbind)
Hmm. According to these articles, if I change the machine password change interval in smb.conf to an impossible value (1,000,000 days), the PDC would never know, and/or care? Is this true? Thanks, Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song -Original Message- From: Wolfram Quester [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 8:44 AM To: [EMAIL PROTECTED] Cc: Mac; Nir Soffer Subject: Re: Weekly machine password changes (RE: RE: [Samba] odd: everything SHOULD work... winbind) Oops, I actually meant http://support.microsoft.com/default.aspx?scid=kb;en-us;Q154501 http://support.microsoft.com/default.aspx?scid=kb;EN-US;q175468 Sorry for that, Wolfi Hi Nir, I think the password changing is initiated by the client. Perhaps these two articles from MS knowledge base are of interest: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q154501 http://support.microsoft.com/default.aspx?scid=kb;en-us;Q154501 I hope this helps, Wolfi -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] 2.2.5 and NIS question
-Original Message- From: Wieprecht, Karen M. [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 2:59 PM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: [Samba] 2.2.5 and NIS question I'm not sure what happe4ned to the --with-nis option either, but it seems to work just fine. Perhaps they made it part of the default set? We use nis and winbind, and NT users with matching UN(IX accounts get assigned the UID and GID I have in NIS. How exactly do you do that? I've only managed to get winbind users when using winbind. smbd would refer to the users in winbind regardless of the users existance in other NSS databases. Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Odd error message in winbind
Hello! On a Linux machine, running Samba 2.2.4, we got this error message: Aug 7 01:47:01 node1-mgmt winbindd[7034]: [2002/08/07 01:47:01, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) Aug 7 01:47:01 node1-mgmt winbindd[7034]: cli_pipe: return critical error. Error was SUCCESS - 0 Previous to that error message, winbindd ran without fault for nearly 30 days. After that error message, we got a few of these sequences: Aug 8 10:19:25 node1-mgmt winbindd[7034]: [2002/08/08 10:19:25, 0] libsmb/cli_netlogon.c:new_cli_nt_setup_creds(209) Aug 8 10:19:25 node1-mgmt winbindd[7034]: new_cli_nt_setup_creds: auth2 challenge failed NT_STATUS_ACCESS_DENIED Aug 8 10:19:25 node1-mgmt winbindd[7034]: [2002/08/08 10:19:25, 0] nsswitch/winbindd_cm.c:cm_get_netlogon_cli(796) Aug 8 10:19:25 node1-mgmt winbindd[7034]: error connecting to domain password server: NT_STATUS_ACCESS_DENIED I'm assuming something in winbindd's state got iffy, and then authentication failed. I don't have access to the PDC to see if maybe the error was caused by an event there, but I was wondering if anyone knows what's going on there. Thanks, Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: Odd error message in winbind
On a Linux machine, running Samba 2.2.4, we got this error message: Aug 7 01:47:01 node1-mgmt winbindd[7034]: [2002/08/07 01:47:01, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) Aug 7 01:47:01 node1-mgmt winbindd[7034]: cli_pipe: return critical error. Error was SUCCESS - 0 Previous to that error message, winbindd ran without fault for nearly 30 days. The DC 'went away'. (Which closed the pipe, and left 0 in the error feild - yes we need a better way do handle this...). I guessed something to that effect, but I don't believe something happened to the DC, that's what's bothering me. I'll need to check that out. So if hit this DEBUG statement DEBUG(0, (cli_pipe: return critical error. Error was %s\n, cli_errstr(cli))); When the error is 0 I should: DEBUG(0, (cli_pipe: Critical error - the pipe has closed. The DC has probably been disconnected) ) or something? need a patch? It looks like the PDC has changed the machine account password on the account, your local machine name has changed or the account on the DC has been deleted. Could the DC have been restored from a backup, with 'old' passwords? I believe not... As I said, I will have to check that out. Anyway, try a rejoin and see if that helps. I was hoping to avoid a machine account reset, or a rejoin, but I assumed that's what I'll have to do anyway. Thanks! Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: Odd error message in winbind
Nir Soffer wrote: On a Linux machine, running Samba 2.2.4, we got this error message: Aug 7 01:47:01 node1-mgmt winbindd[7034]: [2002/08/07 01:47:01, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) Aug 7 01:47:01 node1-mgmt winbindd[7034]: cli_pipe: return critical error. Error was SUCCESS - 0 Previous to that error message, winbindd ran without fault for nearly 30 days. The DC 'went away'. (Which closed the pipe, and left 0 in the error feild - yes we need a better way do handle this...). I guessed something to that effect, but I don't believe something happened to the DC, that's what's bothering me. I'll need to check that out. So if hit this DEBUG statement DEBUG(0, (cli_pipe: return critical error. Error was %s\n, cli_errstr(cli))); When the error is 0 I should: DEBUG(0, (cli_pipe: Critical error - the pipe has closed. The DC has probably been disconnected) ) or something? need a patch? I'll take a patch that actually does the real job - that code needs to be 'upgraded' to NTSTATUS. Follow the functions, and you will eventually get to 'cli_receive_smb()'. This is what is generating the error - so it should probably get the DEBUG(), and a sensible NTSTATUS value should be returned down the chain. Tracking down the code leads me at the end to receive_smb, which probably returns a false when it fails to receive anything. But then again, it could fail on anything, so nailing it down there seems wrong. client_receive_smb appears to be merely a wrapper for receive_smb... Ugh. This stuff is hairy. What exactly needs to happen? Does the code have to see if there's BOTH an error from client_receive_smb, and if there's no status set, and then conclude all it is is a broken link? It's really the BOOLs everywhere that causes the problem. I haven't figured that one out yet - A. What exactly _is_ the construct for keeping a status code, from looking at clierrstr I see that there are 3 classes of error message, each handled sepreately and differently (RAP messages, whatever the hell they may be, NT STATUS messages, and DOS and SMB messages (?!) which are apparently handled together? (?!?) B. Why not return an int value that some meaning like most C functions do? Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: [Samba] Strange crashes and disconnection from PDC?
On Sun, 28 Jul 2002, Nir Soffer wrote: Hmmm, so you do not get core files on your platform either? Is this FreeBSD or something else? I am experiencing the same on FreeBSD, and haven't had time to look into this, as other techniques could give me the info I wanted, but corefiles will be needed for customer installs. I'm using Linux here... From the little I have understood of the code - there are never core dumps on smb_panic regardless of platform since it skips exit_server (I'm still confused on when exactly exit_server _is_ called if smb_panic does the abort() itself, but that's probably just me). I still haven't figured out where exactly someone tells the system 'don't core dump on me', I'm guessing it's just done using a setrlimit for the core size to 0 somewhere, but I still haven't found it. Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song
RE: [Samba] Strange crashes and disconnection from PDC?
Cc:'d to samba-technical
( Background - I'm trying to see how I can get smbd to dump core,
with a user supplied option to allow tell it where to dump it, I'm
poring over the related code)
A 'corefile directory' option might be nice - but we will have to be
careful. Look into smb_panic() and exit_server() for somewhere to
start.
Err. Okay. Can anyone explain me what's up here? From server.c
#if DUMP_CORE
/***
Prepare to dump a core file - carefully !
/
static BOOL dump_core(void)
{
char *p;
pstring dname;
pstrcpy(dname,lp_logfile());
if ((p=strrchr(dname,'/'))) *p=0;
pstrcat(dname,/corefiles);
mkdir(dname,0700);
sys_chown(dname,getuid(),getgid());
chmod(dname,0700);
if (chdir(dname)) return(False);
umask(~(0700));
dump_core is already there, DUMP_CORE is set to 1 (it looks like this
is the default one shipped, btw), yet nothing bloody happens.
The above snippet appears to create a corefiles directory above the log
dir, (which is, I assume, what you want to change using the core
directory
option), but it doesn't create it anywhere I can see after killing a
process with
sig11. What am I missing here?
Also - from what I see, the execution flow of a panic is something like:
exit_servers is set is a fault handler, however in fault_setup (fault.c)
a
SIGSEGV handler is set to sig_fault which calls fault_report which
calls smb_panic which calls abort().
When the heck is exit_servers called, then? And what function does
dump_core perform if there's no one to call it?
I'm probably missing something fundamental here, enlightment will
be appreciated.
Thanks,
Nir.
--
Nir Soffer -=- Software Engineer, Exanet Inc. -=-
Father, why are all the children weeping? / They are merely crying son
O, are they merely crying, father? / Yes, true weeping is yet to come
-- Nick Cave and the Bad Seeds, The Weeping Song
RE: [Samba] RE: FW: samba woes
[Snip - regarding Winbindd over tcp] It's currently rather shoddy, I must admit. New efforts along these lines are definately interesting. I'd love to see the code. Here's what I have so far, only two files needed to be changed, wb_common.c and winbindd.c: Disclaimer: This hasn't been tested a lot. The part where one reads the configuration file stinks (no name resolving, not very robust, and I'm entirely sure that it doesn't leak). Be warned, this is seriously, seriously crappy code. But it did work for me, and after some more testing we will put it in production. The patch is against 2.2.5 - I'm not working with HEAD yet, but I will. I imagine incorporating it into HEAD won't be difficult. Please tell me what you think. The concept is IMO simpler than having some sort of wierd backend where everyone checks the mapping. This way - one winbindd - lots of clients. We do the same (with more robust code, albeit not very suitable for external uses - it uses some propietry libraries and extremely silly ways of getting the port number and IP host to connect to) in a cluster environment and haven't experienced any difficulties. Thanks! Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come -- Nick Cave and the Bad Seeds, The Weeping Song winbindd.c.diff Description: winbindd.c.diff wb_common.c.diff Description: wb_common.c.diff
