similar to: Problem solved? (Was: 2.2.2 printing)

Hello, I am using RH 7.1 with CUPS and a printer connected to it. I also have a windows machine running XP. I have been able to print from windows->linux via samba 2.0.7. Since samba 2.0.7 does not seem to be able to show printer queues with CUPS I tried to upgrade to 2.2.2 (using rpm's from rawhide). I kept my smb.conf file. Initially this worked well and I could manipulate printer

>This is in subversion now. I'll try to get a new release out this >weekend. Thanks! Thanks! But I noticed that giving up the global interpretor lock in a few functions allows other threads to do something stupid (like deleting the shout object during a write). So for everything to be absolutely thread safe a python shout object should contain a mutex and there should be appropriate

>Why would you keep a non-thread safe API ? I do not want to touch libshout. I am only concerned with the python bindings. Probably Brendan can answer this better but I think libshout is not thread safe for simultaneous accesses to a shout_t object. This is not a problem as the posix locking primitives are trivial to use. For python apis should in principle be absolutely thread safe.

OOOOKay. Here's my somewhat silly question. the 2.2.2 whatsnew says: nt acl support This parameter has been changed to a per-share option, and is very useful in enabling Windows 2000 SP2 to load/save profiles from a Samba share. Here's the dilemmna. I have no NT server. However under win9X networking - access control tab, you can either give share level, on a machine by machine

Semms that I've confirmed that all of my problems with Samba arised because of e2compr. After describing my problem to Alan, I've done what I proposed myself last saturday: I've turned off compression in my home directory and tried to save the file several times without modifications, exactly in the same way I've done to reproduce the problem. Et voil?! I could save the file

Attached is a patch against shout-python-0.2 which does two trivial but very useful things (1) The function "get_connected" is exported so that shout-python becomes usable in nonblocking mode. In the current version of shout-python "open" raises an exception in nonblocking mode. (2) The global interpreter lock is released in the potentially blocking functions

I have made a tarball snapshot of Samba pre-2.0.7 available at : ftp://ftp.samba.org/pub/samba/alpha/samba-2.0.7pre1.tar.gz The WHATSNEW.txt file is not yet updated with the list of bugfixes, although the man pages should be up to date with the new options. I'm making this pre1 snapshot available so people can test that this release builds correctly on their systems and can get some

FYI, we've added a wiki page that explains this difference between functional level and schema level in a bit more detail. https://wiki.samba.org/index.php/Windows_2012_Server_compatibility I've got a patch to link to the wiki page from the WHATSNEW (currently pending review/delivery). The other thing to note is there's a bug joining Windows on 4.10 and 4.11rc1. The fix is pending

In problem-fixing, the "nicest" problems are those reproducible on demand. Alas, this one is not nice. System: Samba 2.0.6 on Solaris 2.7 (also see similar on Solaris 2.6). Symptom (user perspective): PC suddenly, spontaneously freezes and eventually the connection times out. Symptom (log file): [2000/02/15 09:27:30, 0] ../lib/util_sock.c:read_socket_data(474)

Okay, I realize at this point that's it's certainly easier for me to just compile 3.0.1 from scratch, but I'm irritated that I can't get patch to work right. Maybe somebody will lead me in the right direction. I've scoured the archives and Google for answers to this, to no avail so far. I'm running Samba 3.0 on Solaris 9. I'm hoping that the new release will help me

Hi all, I just released Samba 2.0.7pre3, available from : ftp://samba.org/pub/samba/alpha/samba-2.0.7pre3.tar.gz This is the third snapshot of the code that should become the official Samba 2.0.7 and is feature complete (ie. I'm only going to accept bug fixes, not more features). This is *not* production code, but should work well as a file and print server, and contains fixes for

Hello Tim, Wow, great documentation! ? That really clears a lot of the terminology? for me. We have to remove our Win2008R2 Servers before Jan2020.?? Hopefully Samba 4.11.x will permit us to join a Win2012R2 Server at a 2008R2 functional level...? Your documentation gives steps on how to do this.? But I need some clarifications... Here's my understanding of the workflow: 1. Upgrade

Hi all, I was in Las Vegas yesterday accepting an award from eWeek and PC Magazine on behalf of Samba for the Innovation in Infrastructure Award in the "Enterprise Software" catagory ! The award was sepcifically for Samba 2.2.2, and we beat out Sun Microsystems Java 2 Platform Standard Edition Version 1.4 and Bea Systems WebLogic Server 7.0 for the award, so I'm stunned that we

Hi all, I was in Las Vegas yesterday accepting an award from eWeek and PC Magazine on behalf of Samba for the Innovation in Infrastructure Award in the "Enterprise Software" catagory ! The award was sepcifically for Samba 2.2.2, and we beat out Sun Microsystems Java 2 Platform Standard Edition Version 1.4 and Bea Systems WebLogic Server 7.0 for the award, so I'm stunned that we

I have subsequently compiled 2.0.7 successfully on Solaris 7, with Sparc 'C' Compiler 5.0. 2.0.7 and previous versions have compiled successfully and work fine on Digital Unix 4.0.D. So have had to abandon 2.2.2 for time being in favor of 2.0.7. Since samba compilations have been successful before, was not logging output :-( The gist of the errors are as follows: Compiler failed on:

Hi, I just installed 2.0.7 on Compaq Tru64 4.0F with options with-quotas and with-utmp. I encountered the following two problems when building smbd : 1- In smbd/quotas.c, one comment is introduced by //. This is not supported by native cc I was using. This is on line : if (save_errno == EDQUOT) /* disk quota exceeded */ 2- As AIX, Tru64 has utmpx.h but 'x functions' are not

Samba Gurus, I've recently built a new Solaris samba server to replace an older one, the older one is running 2.0.7 & the new one is running 2.2.2. I pretty much just copied over the the smb.conf file & made some small adjustments via swat - the options are a bit different. The old server was just the way we needed it.....but now that the new server has gone live it appears we

On 03/25/2011 09:13 PM, Bill Wendling wrote: > On Mar 25, 2011, at 8:44 AM, Michel Alexandre Salim wrote: > >> And in Fedora's Rawhide development tree (not in our upcoming F-15 >> release, since third-party packages won't be ready in time for our May >> release): >> >> http://koji.fedoraproject.org/koji/buildinfo?buildID=235848 >> >> The

Ahh ok, thanks for the clarification!?? I'll go to bed less ignorant tonight ;-) On 2019-07-29 12:07 p.m., Rowland penny via samba wrote: > On 29/07/2019 16:41, Luc Lalonde wrote: >> The first sentence says that default schema has changed from 2008R2 >> (schema 47) to 2012R2 (schema 69). >> >> This does not mean that we're now at Windows 2012R2 functional level

I have a question I hope one of you can help me with. In what version did Samba begin to include support for SMB signing? It looks like 3.0 but I need to be sure. According to http://de.samba.org/samba/whatsnew/samba-3.0.0rc4.html <http://de.samba.org/samba/whatsnew/samba-3.0.0rc4.html> on line 14 is states: 14) Full support for client and server SMB signing to ensure compatibility