date:20071125

[Samba] Joining a win2k3 ads fails

2007-11-25 Thread Lex Brugman

I've just tried the same configuration on a third computer (gentoo on a x86 
platform, just like the
other working box) and it worked, i don't think it is a w2k3 problem
Please note that the problem occurs on an ARM box and is running debian (the 
only difference in
compared to the other 2 boxes where it works).
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re[2]: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)

2007-11-25 Thread Marcin Kucharczyk

Hello,

Sunday, November 25, 2007, 12:25:27 AM, you wrote:

DV [EMAIL PROTECTED] wrote:
 I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, 
 SMP, 6.2 RELEASE). My log.smbd looks like below:

 [...]

 [2007/11/24 16:55:22, 0] 
 /usr/ports/net/samba3/work/samba-3.0.26a/source/lib/pidfile.c:pidfile_create(112)
  

  ERROR: smbd is already running. File /var/run/smbd.pid exists and 
 process id 1961 is running.

 --- /var/run/smbd.pid exists, becase the error is created after 
 unexpected system shutdown...
DV What os the unexpected system shutdown?  Power failure?  Reset button 
DV after system freeze?

The power failure.

 [2007/11/24 16:59:53, 0] lib/util_tdb.c:tdb_log(662)
  tdb(/var/db/samba/gencache.tdb): tdb_reopen: open failed (No such 
 file or directory)
 [2007/11/24 16:59:53, 0] smbd/server.c:open_sockets_smbd(572)
  tdb_reopen_all failed.
 [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632)
  PANIC (pid 2621): tdb_reopen_all failed.
 [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41)
DV The filesystem didn't flush it's buffers on shutdown.  Unexpectedly, 
DV files are missing and/or corrupted that should be there on startup.

Probably corrupted, becouse I checked: the files exist...

 And after start samba works properly until next unexpected system 
 restart  
DV You need to fix this and ensure you're using a journaled file system 
DV with whatever option is available for the safest, most conservative 
DV journaling mode.

The problem started after 3.0.26a upgrade. I had 3.0.32c run without any 
problems.

 Without deleting /var/db/samba, than the samba will start and 
 procedure described on the start of this message will be repeated  
DV You should be able to delete /var/db/samba (plus maybe the pid file) and
DV restart samba.  Samba will create any tdb files it needs like the 
DV initial startup.

Tried ... reinstall was required

Some mor information:

It looks like the same or similar problem:
  http://lists.samba.org/archive/samba/2007-August/134620.html

My system works with ayhlion 64 x2, but I had similar problem on single 
processor configuration: pentium 4 and duron too. The problem apears not only 
after power failure, but also after samba upgrade from ports - make deinstall 
reinstall. /var/db/samba need to be deleted before reinstall becase samba 
3.0.26a has the problem with start with tdb files form 3.0.23c.

-- 
Best regards,
 Marcin  K.  mailto:[EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] FW: Please if you advise

2007-11-25 Thread Abdulhak, Najwa TPD


Dears, 

Any feed back please. 

Najwa
  -Original Message-
 From: Abdulhak, Najwa TPD  
 Sent: Thursday, November 22, 2007 1:31 PM
 To:   'samba@lists.samba.org'
 Subject:  Please if you advise
 
 Dears,
  I've got a problem building samba 3.0.27 on Solaria 8 box.,
 Configuration is successful with ,  ./configure --with-pam --with-syslog
 --with-ldapsam --with-automount  But make gives the following output.
 ###
 Using FLAGS  =  -O -D_SAMBA_BUILD_=3
 -I/export/home/samba/samba-3.0.27a/source/iniparser/src -Iinclude
 -I./include  -I. -I. -I./lib/
 replace -I./lib/talloc -I./tdb/include -I./libaddns -I./librpc
 -DHAVE_CONFIG_H  -D_LARGEFILE_SOURCE -D_REENTRANT -D_FILE_OFFSET_BITS=64 -
 DLDAP_DEPRECATED -DSUNOS5-I/export/home/samba/samba-3.0.27a/source/lib
 -D_SAMBA_BUILD_=3
   PICFLAG= -fPIC
   LIBS   = -lsendfile -lresolv -lnsl -lsocket -ldl
   LDFLAGS= -pie -lthread
   DYNEXP = 
   LDSHFLAGS  = -G -lthread
   SHLIBEXT   = so
   SONAMEFLAG = -Wl,-soname=
 Compiling dynconfig.c
 In file included from include/smb.h:1846,
  from include/includes.h:665,
  from
 /export/home/samba/samba-3.0.27a/source/dynconfig.c:21:
 include/popt_common.h:24:18: popt.h: No such file or directory
 The following command failed:
 gcc  -O -D_SAMBA_BUILD_=3
 -I/export/home/samba/samba-3.0.27a/source/iniparser/src -Iinclude
 -I./include  -I. -I. -I./lib/replace -I./lib
 /talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H
 -D_LARGEFILE_SOURCE -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DLDAP_DEPRECATE
 D -DSUNOS5-I/export/home/samba/samba-3.0.27a/source/lib
 -D_SAMBA_BUILD_=3 -DCONFIGFILE=/usr/local/samba/lib/smb.conf
 -DSBINDIR=/u
 sr/local/samba/sbin -DBINDIR=/usr/local/samba/bin
 -DLMHOSTSFILE=/usr/local/samba/lib/lmhosts
 -DSWATDIR=/usr/local/samba/swat  -DLO
 CKDIR=/usr/local/samba/var/locks -DPIDDIR=/usr/local/samba/var/locks
 -DLIBDIR=/usr/local/samba/lib  -DLOGFILEBASE=/usr/local/samba
 /var -DSHLIBEXT=so -DCONFIGDIR=/usr/local/samba/lib
 -DSMB_PASSWD_FILE=/usr/local/samba/private/smbpasswd
 -DPRIVATE_DIR=/usr/local
 /samba/private -fPIC -c
 /export/home/samba/samba-3.0.27a/source/dynconfig.c -o dynconfig.o
 *** Error code 1
 make: Fatal error: Command failed for target `dynconfig.o'
 ##
 Kindly if you advise
 Najwa
  
 
 
 
 
 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Compiling dynconfig.c with make command

2007-11-25 Thread Abdulhak, Najwa TPD





Dears, 

Any feed back please. 

Najwa
  -Original Message-
 From: Abdulhak, Najwa TPD  
 Sent: Thursday, November 22, 2007 1:31 PM
 To:   'samba@lists.samba.org'
 Subject:  Please if you advise
 
 Dears,
  I've got a problem building samba 3.0.27 on Solaria 8 box.,
 Configuration is successful with ,  ./configure --with-pam --with-syslog
 --with-ldapsam --with-automount  But make gives the following output.
 ###
 Using FLAGS  =  -O -D_SAMBA_BUILD_=3
 -I/export/home/samba/samba-3.0.27a/source/iniparser/src -Iinclude
 -I./include  -I. -I. -I./lib/
 replace -I./lib/talloc -I./tdb/include -I./libaddns -I./librpc
 -DHAVE_CONFIG_H  -D_LARGEFILE_SOURCE -D_REENTRANT -D_FILE_OFFSET_BITS=64 -
 DLDAP_DEPRECATED -DSUNOS5-I/export/home/samba/samba-3.0.27a/source/lib
 -D_SAMBA_BUILD_=3
   PICFLAG= -fPIC
   LIBS   = -lsendfile -lresolv -lnsl -lsocket -ldl
   LDFLAGS= -pie -lthread
   DYNEXP = 
   LDSHFLAGS  = -G -lthread
   SHLIBEXT   = so
   SONAMEFLAG = -Wl,-soname=
 Compiling dynconfig.c
 In file included from include/smb.h:1846,
  from include/includes.h:665,
  from
 /export/home/samba/samba-3.0.27a/source/dynconfig.c:21:
 include/popt_common.h:24:18: popt.h: No such file or directory
 The following command failed:
 gcc  -O -D_SAMBA_BUILD_=3
 -I/export/home/samba/samba-3.0.27a/source/iniparser/src -Iinclude
 -I./include  -I. -I. -I./lib/replace -I./lib
 /talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H
 -D_LARGEFILE_SOURCE -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DLDAP_DEPRECATE
 D -DSUNOS5-I/export/home/samba/samba-3.0.27a/source/lib
 -D_SAMBA_BUILD_=3 -DCONFIGFILE=/usr/local/samba/lib/smb.conf
 -DSBINDIR=/u
 sr/local/samba/sbin -DBINDIR=/usr/local/samba/bin
 -DLMHOSTSFILE=/usr/local/samba/lib/lmhosts
 -DSWATDIR=/usr/local/samba/swat  -DLO
 CKDIR=/usr/local/samba/var/locks -DPIDDIR=/usr/local/samba/var/locks
 -DLIBDIR=/usr/local/samba/lib  -DLOGFILEBASE=/usr/local/samba
 /var -DSHLIBEXT=so -DCONFIGDIR=/usr/local/samba/lib
 -DSMB_PASSWD_FILE=/usr/local/samba/private/smbpasswd
 -DPRIVATE_DIR=/usr/local
 /samba/private -fPIC -c
 /export/home/samba/samba-3.0.27a/source/dynconfig.c -o dynconfig.o
 *** Error code 1
 make: Fatal error: Command failed for target `dynconfig.o'
 ##
 Kindly if you advise
 Najwa
  
 
 
 
 
 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)

2007-11-25 Thread Doug VanLeuven


Marcin Kucharczyk wrote:

DV You should be able to delete /var/db/samba (plus maybe the pid file) and
DV restart samba.  Samba will create any tdb files it needs like the 
DV initial startup.


Tried ... reinstall was required

Some mor information:

It looks like the same or similar problem:
  http://lists.samba.org/archive/samba/2007-August/134620.html

My system works with ayhlion 64 x2, but I had similar problem on single 
processor configuration: pentium 4 and duron too. The problem apears not only 
after power failure, but also after samba upgrade from ports - make deinstall 
reinstall. /var/db/samba need to be deleted before reinstall becase samba 
3.0.26a has the problem with start with tdb files form 3.0.23c.
  

Better file a bug report then.
https://bugzilla.samba.org/enter_bug.cgi


Regards, Doug

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)

2007-11-25 Thread Volker Lendecke

On Sun, Nov 25, 2007 at 05:29:52AM -0800, Doug VanLeuven wrote:
 Marcin Kucharczyk wrote:
 DV You should be able to delete /var/db/samba (plus maybe the pid file) 
 and
 DV restart samba.  Samba will create any tdb files it needs like the 
 DV initial startup.
 
 Tried ... reinstall was required
 
 Some mor information:
 
 It looks like the same or similar problem:
   http://lists.samba.org/archive/samba/2007-August/134620.html

This particular bug report is highly unlikely to be a Samba
problem. Also, I have a hard time to believe that you have
to really deinstall Samba after a system crash. It *is*
definitely possible to restart Samba from whatever state the
system is in, possibly by removing tdb files. Removing and
recompiling the daemons is definitely unnecessary. You might
want to see what this removing/reinstalling really does.

Volker


pgpUHOVqv12lL.pgp
Description: PGP signature
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] connection to IPC$ denied due to security descriptor

2007-11-25 Thread richid

I don't have any valid users directive set in my global section either.
Your confs look good to me Karol, but what do I know? Maybe someone else
can shed some light on this...

Karol Makowski wrote:

Marc-Henri PAMISEUX pisze:
I've just find why ;)
It's in my smb.conf, there is a problem with directive:
valid users = @SmbDomAdmins,@SmbDomUsers,@SmbDomGuests,@SmbUsers
please, comment it !

I don't have any valid directives in my global section.
There must not be any valid users directive in the Global section. By
the way, you have to set it in each share definition.

There are not
I hope that it will be resolv your error ;)
If my answer did not give you satisfaction, can you post your smb.conf
file ?

Ok, http://prozac.bsdzine.org/~spaceman/samba

I hope someone will find any errors. As i wrote before I can access
shares and I can join domain, but
I can't log into it.

--
Karol Makowski
KOELNER SA IT Department
mailto: [EMAIL PROTECTED]
[mobile: +48 661 94 00 57] [office: +48 71 32 09 287]
jid: [EMAIL PROTECTED]

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

--
View this message in context:
http://www.nabble.com/connection-to-IPC%24-denied-due-to-security-descriptor-tf4828629.html#a13937265
Sent from the Samba - General mailing list archive at Nabble.com.

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

[Samba] NT_STATUS_NO_LOGON_SERVERS errors sporadically occurring

2007-11-25 Thread Jason Haar

Hi there

I have samba-3.0.27a rolled out over a large number of servers, and
every once in a while one of them will start failing to allow people to
connect, with winbind reporting NT_STATUS_NO_LOGON_SERVERS, and
ntlm_auth failing with NT_STATUS_NO_LOGON_SERVERS: No logon servers.
The same problem occurred with earlier versions too.

I think I've tracked down the cause of the problem as being our fault,
but Samba really isn't handling it well. We have a 10.* network, and
servers with dual Ethernet cards, and sometimes/somehow the IP address
of the unused 2nd card (a 192.168.* address) starts getting broadcast
onto our Active Directory as being a domain controller IP. Then if
winbind decides to choose that address, it all starts failing, as that
address space isn't reachable.

If I do a nslookup domain.AD I get a listing of all our valid DC 10.*
addresses back - plus the unwanted 192.168 address - but it appears that
sometimes winbind decides that is the valid address, and won't try any
of the other addresses? And then you get the NT_STATUS_NO_LOGON_SERVERS
- as it isn't reachable.

Here's some excepts from /var/log/samba/log.wb-DOMAIN


ads_find_dc: looking for realm 'domain.AD'
get_sorted_dc_list: attempting lookup for name  domain.AD (sitename
NULL) using [ads]
sitename_fetch: Returning sitename for  domain.AD: correct-sitename
name domain.AD#20 found
get_dc_list: negative entry domain.AD removed from DC list
get_dc_list: returning 1 ip addresses in an ordered list
get_dc_list: 192.168.234.235:389


those last two lines imply why this problem occurs, but this problem
isn't being noticed within AD itself - I think Microsoft actually uses
ICMP pings to test DCs are reachable? Does Samba? Also, I have no idea
why it returns only one, invalid IP - nslookup shows this particular
domain has 13 domain controller IPs listed - including the one 192.168 one.

Obviously to fix it I just have to whine at our AD people until they
clean out this bogus DC IP - but shouldn't Samba work its way around
this? As an added advantage, ping tests could even ensure Samba connects
to the closest DC by measuring the latency...?

Thanks!

-- 
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] NT_STATUS_NO_LOGON_SERVERS errors sporadically occurring

2007-11-25 Thread Jeremy Allison

On Mon, Nov 26, 2007 at 09:51:18AM +1300, Jason Haar wrote:
 
 If I do a nslookup domain.AD I get a listing of all our valid DC 10.*
 addresses back - plus the unwanted 192.168 address - but it appears that
 sometimes winbind decides that is the valid address, and won't try any
 of the other addresses? And then you get the NT_STATUS_NO_LOGON_SERVERS
 - as it isn't reachable.
 
 Here's some excepts from /var/log/samba/log.wb-DOMAIN
 
 
 ads_find_dc: looking for realm 'domain.AD'
 get_sorted_dc_list: attempting lookup for name  domain.AD (sitename
 NULL) using [ads]
 sitename_fetch: Returning sitename for  domain.AD: correct-sitename
 name domain.AD#20 found
 get_dc_list: negative entry domain.AD removed from DC list
 get_dc_list: returning 1 ip addresses in an ordered list
 get_dc_list: 192.168.234.235:389
 
 
 those last two lines imply why this problem occurs, but this problem
 isn't being noticed within AD itself - I think Microsoft actually uses
 ICMP pings to test DCs are reachable? Does Samba? Also, I have no idea
 why it returns only one, invalid IP - nslookup shows this particular
 domain has 13 domain controller IPs listed - including the one 192.168 one.
 
 Obviously to fix it I just have to whine at our AD people until they
 clean out this bogus DC IP - but shouldn't Samba work its way around
 this? As an added advantage, ping tests could even ensure Samba connects
 to the closest DC by measuring the latency...?

We should notice this address is bad and add it to the negative
connection cache once we fail to connect - we actually use a lot
of techniques to ensure we don't get stuck on a bad DC (server
affinity cache, negative connection cache etc.). Is there a
chance you can get me a debug level 10 when you're running into
this problem so I can see what is going on ?

Jeremy.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] connection to IPC$ denied due to security descriptor

2007-11-25 Thread Edmundo Valle Neto


richid escreveu:

Hey all,

I have a fileserver running Debian Etch and Samba 3.0.24 that I use to serve
media and private home directories.  I have a couple roommates, and
therefore have a couple accounts on the box for those users.  I had
everything working perfectly until last week when my system drive took a
crap.  I've reinstalled everything exactly the same (I think?) but now I am
having problems with some accounts not being able to connect to the shares. 
My username can connect to my home share and the communal media share just

fine.  When I try to connect to another users home share or to the media
share with their username, I keep getting the password dialog box.  I've
ensured that they are in smbpasswd and that their password is correct.  I've
also verified this using smbclient.  


DETAILS:

The log file is reporting this error when I try to connect:
make_connection: connection to IPC$ denied due to security descriptor.

Here is output from smbclient:
[EMAIL PROTECTED]:~$ smbclient //warehouse/media -U bob
Password: 
Domain=[WAREHOUSE] OS=[Unix] Server=[Samba 3.0.24]

smb: \ ls
  .   D0  Thu Oct 18 11:25:22
2007
  ..  D0  Wed Nov  7 21:47:06
2007
  audio   D0  Tue Nov 13 23:40:25
2007
  downloads   D0  Tue Nov 13 23:41:11
2007
  video   D0  Thu Nov 15 23:00:34
2007

44708 blocks of size 33553920. 25310 blocks available
smb: \ 


Here is my smb.conf:

[global]
   netbios name = warehouse
   server string = warehouse
   dns proxy = no
   log file = /var/log/samba/log.%m
   max log size = 1000
   syslog = 0
   panic action = /usr/share/samba/panic-action %d
   security = user
   encrypt passwords = true
   passdb backend = tdbsam
   obey pam restrictions = yes
   invalid users = root
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n 
   socket options = TCP_NODELAY

   domain master = auto

force user = %U
force group = users

[homes]
   comment = Home Directories
   browseable = no
   writable = yes
   create mask = 0700
   directory mask = 0700
   force group = %G
   valid users = %S

[media]
   comment = Media
   path = /mnt/storage/media
   browsable = yes
   writeable = yes
   create mask = 0775
   directory mask = 0775
   #guest ok = yes
   hide files = /*.dat/


It's pretty basic, I'm not doing anything special here.  Anyone have any
idea what the problem is?  I've also read a couple other threads, and have
already tried removing the /var/run/samba/share_info.tdb file and restarting
Samba, but that hasn't worked.  I'm really stumped on this one, anyone else?

Thanks in advance,
Rich
  


I have something similar with the computers in my home using Ubuntu 
(that uses almost the same samba package), I can say one thing, it 
doesn't seems to triggered with something inside share_info.tdb, putting 
the line force group = users (that I think I never used before) gives 
me make_connection: connection to IPC$ denied due to security 
descriptor. errors when I log on a Windows XP in the same network, and 
it appears to happen when XP tries to connect to samba with the guest 
account to get the list of shares. But I haven't noted any problem 
because of that. Samba continues to accept connections using already 
created accounts.


So, I don't have sure if your problem has anything to do with that error 
message.


Testparm gives you any error?
Listing the shares with these accounts work? smbclient -L localhost 
-Uanyuser%password ?


Regards.

Edmundo Valle Neto
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[SCM] Samba Shared Repository - branch v3-2-test updated - initial-v3-2-unstable-368-g41e0768

2007-11-25 Thread Volker Lendecke

The branch, v3-2-test has been updated
   via  41e07682dc1fa535ddaf405efa26fabb33c8bbf9 (commit)
  from  85a84f72ffc440fb71744cb72de2dba07793123c (commit)

http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test


- Log -
commit 41e07682dc1fa535ddaf405efa26fabb33c8bbf9
Author: Volker Lendecke [EMAIL PROTECTED]
Date:   Sun Nov 25 12:54:52 2007 +0100

In libsmbclient, map NT_STATUS_OBJECT_PATH_NOT_FOUND to ENOENT

Thanks to SATOH Fumiyasu!

This fixes bug 4974

---

Summary of changes:
 source/libsmb/clierror.c |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)


Changeset truncated at 500 lines:

diff --git a/source/libsmb/clierror.c b/source/libsmb/clierror.c
index 2232ee2..c9c5a6c 100644
--- a/source/libsmb/clierror.c
+++ b/source/libsmb/clierror.c
@@ -239,6 +239,7 @@ static const struct {
 {NT_STATUS_INVALID_HANDLE, EBADF},
 {NT_STATUS_ACCESS_DENIED, EACCES},
 {NT_STATUS_OBJECT_NAME_NOT_FOUND, ENOENT},
+{NT_STATUS_OBJECT_PATH_NOT_FOUND, ENOENT},
 {NT_STATUS_SHARING_VIOLATION, EBUSY},
 {NT_STATUS_OBJECT_PATH_INVALID, ENOTDIR},
 {NT_STATUS_OBJECT_NAME_COLLISION, EEXIST},


-- 
Samba Shared Repository

svn commit: samba r26111 - in branches/SAMBA_4_0/source/torture/rpc: .

2007-11-25 Thread vlendec

Author: vlendec
Date: 2007-11-25 13:38:07 + (Sun, 25 Nov 2007)
New Revision: 26111

WebSVN: 
http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=revroot=sambarev=26111

Log:
Fix an uninitialized variable
Modified:
   branches/SAMBA_4_0/source/torture/rpc/dfs.c


Changeset:
Modified: branches/SAMBA_4_0/source/torture/rpc/dfs.c
===
--- branches/SAMBA_4_0/source/torture/rpc/dfs.c 2007-11-25 04:53:54 UTC (rev 
26110)
+++ branches/SAMBA_4_0/source/torture/rpc/dfs.c 2007-11-25 13:38:07 UTC (rev 
26111)
@@ -503,7 +503,7 @@
const char *dir = SMBTORTURE_DFS_DIRNAME;
const char *path = SMBTORTURE_DFS_PATHNAME;
struct smbcli_state *cli;
-   bool ret;
+   bool ret = true;
 
printf(Testing StdRoot\n);

33 matches

Mail list logo