similar to: Threaten warnings while compiling Samba 2.2.7a on Solaris 2.5.1

Hi, Compilation fails on Solaris 7 + GCC and Solaris 2.5.1 + SUN CC. Each time the problem is on winbind. I have no idea about what's going wrong. I didn't have any trouble with SAMBA 3.0.21rc1. Can you help me ? Thank you, Pierre --------- SOLARIS 7 --------- Configure ./configure --with-acl-support --with-ldap=no --disable-cups --enable-static=yes --with-included-popt --------

Hi, I have just compiled and linked Samba 2.2.7a on a Solaris 8 server with the GCC 2.95.3 version compiler. I get the following compilation warnings. Can i still use the software without a expected crash? Compiling passdb/secrets.c passdb/secrets.c: In function `secrets_named_mutex': passdb/secrets.c:287: warning: passing arg 2 of `tdb_lock_bystring' discards qualifiers from pointer

Hello, I had the pleasure of installing a new Linux(RH8.0)/Samba(2.2.7a) server (as a PDC) at one of our locations this week. They previously were accessing a shared drive from a Win2k Pro. machine. The migration did not go very smooth. Most things have been resolved, but we have some strange issues that are still causing problems, which I was hoping someone out there would have some insight

I would really appreciate help ! I did not have any reply to my two posts and I don't know what to do. I can't build 3.0.21a and I have to migrate 54 Solaris 2.5.1 servers from 2.2.8a to 3.0.x. I'm afraid we could not move to newer solaris versions before 12 or 18 months. Under is the problem description. Thank you for your help. Pierre --------- SOLARIS 7 --------- On Solaris 7

Good Morning, I recently compiled Samba 2.2.7a as a 64bit executable on Solaris 8. The Solaris 8 server is configured to permit 65535 files to be open, while Samba has been configured to allow 65500 files to be open. These large number of files are required to permit simulataneous compilations to take place a single build server, though there are multiple build servers. Last time I tried to

On Apr 7, 2009, at 6:02 PM, Tanya M. Lattner wrote: > Can you please just respond to the specific patch on llvm-commits > instead > of emailing llvm-dev? Don't happen to know which checkin caused it...

Hello, I had downloaded the samba 2.2.7a tarball, the pubkey and the samba-2.2.7a.tar.asc files from your website. The import of the samba-pubkey.asc works probably, but by the verify I get the errormessage that no path to this signature is defined and the signature can't verified. The distribution of Linux is the SuSE 8.0 and I used this lines. gpg --import samba-pubkey.asc

________________________________ From: Uday Mhatre<mailto:uday_mhatre at hotmail.com> Sent: ?05-?12-?2014 12:58 To: Andrea Venturoli<mailto:ml at netfence.it> Subject: RE: [Samba] samba 2.2.7a tech issue Just wondering if these samba versions are backward compatible with fedora14 and other Linux distributions. Regards, Uday ________________________________ From: Uday

Hi, My last post about compilation problems of 3.0.21 on Solaris 2.5 and 7 has no answer,so I investigated a bit more further to try to find out the differences with 3.0.20b. Problems come from winbind_nss_solaris.c witch evolved a lot in 3.0.21. Several references are done to struct in6_addr witch are not defined on solaris 7 and older. If I'm not wrong in my diagnostic, is there a

I wonder how to configure the name resolution on the Windows network. I am puzzled by the "Wins Support" section of the smb.conf man page: " You should not set this to yes unless you have a multi-subnetted network and you wish a particular nmbd to be your WINS server " Does that mean that on my subnet, broadcast is as performant as direct acces to the Name Server, even if

Dear all, Many months ago John Terpstra took time and helped this newby get samba 3.0 installed and working really well on my server at the time. Unfortunately the server died on me. Now I have a new one I am attemping to install Samba 3 on but i get this conflict with version 2.2.7a that came with RH 9. I can not remove it. I have tried several methods and it still there cause 3.0 will not

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the release of Samba 2.2.7a. This is the latest stable release of Samba and the version that all production Samba servers should be running for all current bug-fixes. The source code can be downloaded from : http://download.samba.org/samba/ftp/ in the file samba-2.2.7a.tar.gz or samba-2.2.7a.tar.bz2. Both

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the release of Samba 2.2.7a. This is the latest stable release of Samba and the version that all production Samba servers should be running for all current bug-fixes. The source code can be downloaded from : http://download.samba.org/samba/ftp/ in the file samba-2.2.7a.tar.gz or samba-2.2.7a.tar.bz2. Both

pk. I am now running Samba-2.2.7a and RedHat 8, and i am still having a problem with files > 2gb in size. after i mount a Windows share, I can't create large files on it. #ulimit -f unlimited #mount -t smbfs -o username=3D'Administrator',password=3D'***' //x.x.x.x/C$ /mnt/win2kserver_cdrive which successfully mounts the windows share on my linux box. but if i=20 #dd

I have 2 Sun servers. One is running Samba 2.0.7 and I have no problems with response time or performance. The other server is running Samba 2.2.7a and on this server there are performance issues, slowness and long response times with long latencies over 400 msec. Both Sun server's are running SunOS 5.8. Is Samba 2.2.7a supported on this Unix box or is for a Linux server? Should I be

I just tried upgrading from 2.2.3 to 2.2.7a on my PDC (2.2.17 kernel). The logon script that I have been using all along without any problems quits executing w/ 2.2.7a. I can manually map the netlogon share after logging in and manually run the script and everything work fine. No error messages appear in the log files. My smb.conf file is included. Don't know quite where to go with this

Hi, I have one NT4 PDC that needs to be migrated to Samba-PDC. No Active Directory. Just users, groups, windows shares... the works. I'm seeing that Samba-3.x is "very PDC-oriented". I like that. But, so far, Samba-3 is still in beta/pre-release versions and in my "stock" distribution, Samba is on 2.2.7a version (2.2.7a-security-rollup-fix). Should I wait for Samba-3?

On Wed, Jan 7, 2009 at 11:05 AM, ajay ohri <ajayohri at yahoo.com> wrote: > > FYI..not a R -Help Topic, buy I dont know which list to post discussions like this. > Regards, > Ajay > > ---------- Forwarded message ---------- > From: ajay ohri <ajayohri at yahoo.com> > Date: Wed, Jan 7, 2009 at 10:46 AM > Subject: Re: R "Threatens" SAS, According to

Object: Command "configure" aborted (with samba 2.2.7a and 2.2.8a) on HP-UX 11.0 Hello, The command ./configure has aborted: cd ..../samba-2.2.7a/source ./configure ............................... checking whether struct passwd has pw_age... yes checking for poptGetContext in -lpopt... no checking whether to use included popt... ./popt checking configure summary... WARNING: No

Hello, we tried upgrading from 2.2.4 to 2.2.7a in order to fix a problem. We believe it fixes it, BUT, 2.2.7a causes logon scripts to never run. That is, we have 2.2.4 installed and the logon procedure works perfectly. We then upgrade the samba/samba-common (debian) packages, and everything works *except* that logon scripts never run. What are the possible causes for such a thing? Thanks! --