similar to: smbclient, find, and NetBSD (fwd)

Dear developers, I often use smbclient from NetBSD 1.5 (i386) to an NT4.6a box. When I leave recursion off and do an 'mput', the find fails because NetBSD's find does not have the '-maxdepth' option. The problem is in samba/source/client/client.c at line 1168. Here is the code that causes the problem with a temporary fix. > if (recurse) >

Hi, There is a problem with smbclient mput ( maybe more, I haven't checked ) with the SAMBA CVS I checked out on March 14, 2000. The problem will manifest itself on systems that don't support -maxdepth on the find command. (AIX being one of them ). I compared source/client.c between 2.0.6 and the cvs. The problem is in: static void cmd_mput(void) When recurse=false Version 2.0.6

Hi, We (NetBSD) just received a bug report that smbclient's mput command usees find(1) with a non-standard option "-maxdepth". This was replaced with a simple call to ls(1). As I don't know how many of the patches from out Packages Collection were sent to you in the past, I'm simply sending you all our patches - please include any you like in future samba releases! BTW,

I've just fixed a bug (#528 in bugzilla) to do with wins hook functionality. The wins hook parameter is broken in Samba 3.0.0 but will be fixed in 3.0.1. The attached patch against the release samba-3.0.0.tar.gz file can be used to fix it. Tim. -------------- next part -------------- Index: nmbd_winsserver.c =================================================================== RCS file:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Potential Denial of Service bug in smbd == CVE ID#: CVE-2007-0452 == == Versions: Samba 3.0.6 - 3.0.23d (inclusive) == == Summary: A logic error in the deferred open code == can lead to an infinite loop in smbd ==

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Potential Denial of Service bug in smbd == CVE ID#: CVE-2007-0452 == == Versions: Samba 3.0.6 - 3.0.23d (inclusive) == == Summary: A logic error in the deferred open code == can lead to an infinite loop in smbd ==

Hi, I'm new to the list, I hope i'm posting at the right place ;) I'm having a hard time trying to update and to move my Samba 2.2 PDC to a new Debian server. Currently, the PDC is using Samba 2.2.8 on a Solaris Server. My goal is to move it to another computer, and to update it to a newer version (3.0.24) This must be fully transparent for the users, since I have no time to

I get the following compile error when compiling p8 with p4 Makefile: Linking smbd util.o: In function `check_log_size': util.o(.text+0x2cc): undefined reference to `slprintf' util.o: In function `name_mangle': util.o(.text+0x94f): undefined reference to `slprintf' util.o: In function `standard_sub_basic': util.o(.text+0x4c9e): undefined reference to `slprintf' util.o: In

Hi, I hope this gets picked up by some bug marshall ... I have downloaded (yesterday) the 1.2 branch from svn ... When running: asterisk -vvvvc loaded modules: [modules] autoload=no load => pbx_functions.so load => pbx_config.so load => codec_a_mu.so load => format_pcm_alaw.so load => codec_ulaw.so load => codec_alaw.so load => format_pcm.so load => func_uri.so

[Derek, I'm cc'ing the Samba list so that others can chime in.] Derek Winkler <derek@aim-systems.on.ca> wrote: > > Having a couple problems with Samba: > > First Samba 1.9.18p6 doesn't compile under SCO Unix 3.2v4.2: > > Linking smbd > undefined first referenced > symbol in file > getpagesize

I recently upgraded to 18p8 from 16p11 and found that smbclient now needed a -W in order to connect properly to our domain (which was not the name supplied with the -DWORKGROUP= from the make). Turns out that clientutil.c always uses the value specified by the WORKGROUP macro and never calls lp_workgroup() to get the value specified in the smb.conf file, unless WORKGROUP is "".

I am trying to compile pwlib in order to get h323 support working. Most of the compile is fine except it falls over at the point below. Does anyone have a solution? Thanks Johan make[2]: Entering directory `/root/pwlib/tools/asnparser' g++ -o obj_linux_x86_r/asnparser -Wl,--gc-sections -s -L/root/pwlib/lib ./obj_linux_x86_r/asn_grammar.o ./obj_linux_x86_r/asn_lex.o

Following is the errors when I tried to compile oh323 in FreeBSD 5.3. Asterisk is updated from cvs. asterisk# gmake for x in wrapper asterisk-driver; do gmake -C $x build || exit 1 ; done make: illegal option -- - usage: make [-BPSXeiknqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable]

hi*& Samba has troubles with joining to NT PDC, that has some scope id because: 1. smbpasswd does not know anything about scope id and you haven't any chance to join into NT PDC. 2. also many utils like smbmount doesn't know scope id 3. In smbclient you can specify scope id, but you should remember it and etc. It's not so usable. I'm asked about these problems in samba

Here's a second set of diffs for sanity-checking smb.conf files. This one implements a basic set of checks on netbios names. No, it won't recognize someone using an ip address, but it will realize the dots don't belong: $ testparm Load smb config files from /usr/local/samba/lib/smb.conf WARNING: netbios name "127.0.0.1" contained a dot, which is only legal in DNS domain

I'm trying to make the chan_h323 in /usr/src/asterisk/channels/h323 But I'm getting all kinds of errors about PWLIB... I built using the newest PWLIB and OpenH323 from CVS Error log from make below make g++ -g -c -fno-rtti -o ast_h323.o -march=i686 -DPBYTE_ORDER=PLITTLE_ENDIAN -DNDEBUG -DDO_CRASH -DDEBUG_THREADS -pipe -Wall -fPIC -DP_LINUX -D_REENTRANT -D_GNU_SOURCE -DP_HAS_SEMAPHORES

I'm trying to make the chan_h323 in /usr/src/asterisk/channels/h323 But I'm getting all kinds of errors about PWLIB... I built using the newest PWLIB and OpenH323 from CVS Error log from make below make g++ -g -c -fno-rtti -o ast_h323.o -march=i686 -DPBYTE_ORDER=PLITTLE_ENDIAN -DNDEBUG -DDO_CRASH -DDEBUG_THREADS -pipe -Wall -fPIC -DP_LINUX -D_REENTRANT -D_GNU_SOURCE -DP_HAS_SEMAPHORES

PArdon the "newbie" nature of this question, but I *am* a samba newbie I'm trying to compile samba-1.9.18p6 on a DEC Alpha running OSF/1 V3.0 (I know it's old, but I'm stuck with it). I've modified the Makefile as follows... ># Add any optimisation or debugging flags here ># add -DSYSLOG for syslog support >FLAGS1 = -O -std1 -w >LIBS1 = and ># This

Great job on SWAT. I'm a hard-core UNIX guy, and I like my vi and whatnot. But it's nice to see a functional web interface. It could use some more work--but great job so far! Anyway, I found a core-dump-causing-bug. I was curious as to whether or not swat limited addition of passwords to the smbpasswd file by the users that exist in the system's /etc/passwd file. I was relativly

(This may be a repost; but I was not subscribed to the list and looking at the current archives the articles are not showing up.) Great job on SWAT. I'm a hard-core UNIX guy, and I like my vi and whatnot. But it's nice to see a functional web interface. It could use some more work--but great job so far! Anyway, I found a core-dump-causing-bug. I was curious as to whether or not swat