similar to: couple of minor issues with the Samba 3.0.8 release

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For anyone interested in testing some printing fixes: I've just uplaoded a moderate sized patch for Samba 3.0.7 that addresses the following bugs: https://bugzilla.samba.org/show_bug.cgi?id=1519 https://bugzilla.samba.org/show_bug.cgi?id=1679 Both fixes have been checked in for incusion in the next 3.0.8 preview release. The patch for 3.0.7

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For people with print servers: I'm working on fixing a bug for 3.0.8 and need to know how many people use smb.conf variables other than the standard printing vars like %p, %j, etc... in the various printing commands. Please send me examples if you use things like %U, or %m. Thanks. cheers, jerry -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. There have been several important issues fixes since the 3.0.6 release. See the "Changes" section for details on exact updates. Common bugs fixed in 3.0.7 include: ~ o Fixes for two Denial of Service

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To all list subscribers: This list now requires that all posts be approved by a moderator including those appearing to come from a *@samba.org address. This will prevent situations such as occurred yesterday when an email worm forged a samba.org address (my own) and bounces began filtering back through the samba-announce list. We apologize for the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Attention all administrators of Samba 2.2.x installations: The Samba 2.2 code base has been in maintenance mode for several months (since the release of Samba 3.0.0) with no active development currently taking place. Samba 3.0 is now firmly established and we feel that it is time to declare an end-of-life for Samba 2.2. The main implication is that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For those using Samba with OpenLDAP: I've posted and updated schema file for use with OpenLDAP 2.x at http://samba.org/~jerry/patches/post-3.0.6/samba.schema This file should replace the patch I posted earlier today. Sorry for the confusion. cheers, jerry - --------------------------------------------------------------------- Alleviating the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If you are having any printing issues and upgrading from 3.0.2a to v3.0.3 or later, please read this: Prior to Samba 3.0.3, Linux system were incorrectly tagged as using BSD printing by default even if cups support was detected. Ironically, this was correct for many systems that had the cups-devel package installed but still ran lpd. Samba 3.0.3

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We are working on getting 3.0.8pre1 out this week. There's been a fair amount of changes that were held back from 3.0.7 so its time to get another preview release out. Also, I'm working on the first 3.1.0. The is essentially a copy of trunk. As a reminder, the purpose of the 3.1.x releases is similar to what we've used the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can't remember who this was. Anyways, I'm trying to corelate the memory leak with 'disblae spoolss = yes' and need some more data points. Thanks. cheers, jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just checked in a change that will be in 3.0.11pre2 (when it is released) that allows members of the Domain Admins group (defined by the Samba DC's group mapping table) to join clients to the domain. You can get the port for 4.0.10 from http://www.samba.org/~jerry/patches/post-3.0.10/domain_admin-join.patch Please test and send me any

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If you reported a problem reading files from XP (or other clients) after upgrading to Samba 3.0.6, please try the following smb.conf setting and let me know if this solves it for you. [global] use sendfile = no Thanks. cheers, jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm)

Thanks a lot! That would be great if you can explain further why and how the netbios session requires the netbios name, not ip address, Thanks again! Cheers Jason -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Friday, January 07, 2005 10:42 AM To: Chu, Xingjun [CAR:9D10:EXCH] Cc: 'samba@lists.samba.org' Subject: Re: [Samba] "Called name

Hello, the problem with this error is, allthough I tried both settings, I upgraded from 2.2.3a to 2.2.12 because of a bug in rpcclient - > adddriver. The configuration is still untouched. Even when I switch back to 2.2.3a it doesn't work. And now the funny thing, I have a second box which is configured/compiled exactly the same way as the first one, and on this box it works regards

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded a new draft of the printing patch for 3.0.10 to http://www.samba.org/~jerry/patches/post-3.0.10/ The only change is a small fix to fix the register_message_flags() error messages in the logs. After some thought, I think this might address the 'jobs failing to be removed from the queue list' bug. If people could test and let

I do if you're interested... -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Monday, August 23, 2004 11:45 AM To: mlueck@lueckdatasystems.com Cc: samba@lists.samba.org Subject: Re: [Samba] Update -> Someone with "Access Denied" from Windows plstry this test to compare notes with me -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. There have been several important issues fixes since the 3.0.6 release. See the "Changes" section for details on exact updates. Common bugs fixed in 3.0.7 include: ~ o Fixes for two Denial of Service

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mostly for print server admins: I am considering marking testprns as deprecated (or just remove it). It doesn't seem to be that useful anymore. Does anyone use it on a regular basis and would therefore be distraught if it were gone in a future 3.0.x release ? cheers, jerry -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks to Martin and Walter for pointing out that this is an old XP bug. Here's the link: http://support.microsoft.com/default.aspx?scid=kb;en-us;329234 Unless someone can provide more information to show that this is not the bug you are seeing with "slow printing from xp sp2 clients", I'm marking this one off my list. Some old

Hello, well the problem at least partly solved - only the test page can not be printed, all other documents work. regards Christoph ------- Forwarded message follows ------- From: "Christoph Galuschka" <christoph.galuschka@tikom.at> Organization: Ti.KOM Tirol Kommunikation GmbH To: samba@lists.samba.org Date sent: Wed, 05 Jan 2005 16:50:54 +0100

Hi Jerry, First, thanks a lot for the answers! In regards, to your reply, can you provide a little bit more precisions here: 1. The question 1 was about not using winbindd when in ADS security mode. Is the answer still Yes? I know that it is true when in DOMAIN security mode. 2. About Question 6, from your answer, my understanding is that the Samba server must be in the same domain as the