Displaying 20 results from an estimated 5000 matches similar to: "clarification on recent printing threads"
2004 Dec 03
1
who reported the memory leak in the printing code 3.0.[8|9]
-----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
2005 Jan 05
1
new printing patch for 3.0.10 may fix the 'failure to remove print jobs from queue list display'
-----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
2004 Oct 19
1
largosh printing patch for Samba 3.0.7
-----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
2004 Oct 18
3
polling for options on printing commands
-----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
-
2004 Sep 13
0
Samba 3.0.7 Available for Download
-----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
2004 Dec 14
0
all posts are now moderated
-----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
2004 Jul 22
0
Oct 1, 2004 -- End-Of-Life for Samba 2.2.x
-----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
2004 Aug 20
0
updated OpenLDAP schema file for 3.0.6
-----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
2004 Sep 23
0
upcoming releases (3.0.8pre1 and 3.1.0)
-----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
2004 Nov 09
0
couple of minor issues with the Samba 3.0.8 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For anyone building Samba from source:
I goofed a couple of small details in the 3.0.8 release.
(a) the docs are the ones from 3.0.8pre2. The latest docs
~ build can be downloaded from
~ http://samba.org/~samba-bugs/docs/samba-docs-latest.tar.bz2
~ Just unpack this archives and move the contents into
~ samba-3.0.8/docs/
(b) for some
2005 Jan 06
0
Patch available to address the 'joining clients using root account' limitation
-----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
2004 Aug 30
0
Attention - people who reported problems reading files from XP after upgrade to 3.0.6
-----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)
2005 Jan 07
1
"Called name not present" - using smbclient from linu x to access win98
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
2005 Jan 05
0
(Fwd) Re: second samba problem
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
2004 Aug 23
1
Update -> Someone with "Access Denied" from Windows plstry this test to compare notes with me
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
2004 Sep 13
1
Samba 3.0.7 Available for Download
-----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
2004 Dec 23
3
time for a poll -- does anyone use the testprns tool ?
-----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
-
2004 Nov 30
2
XP bug -- client spooler loop (MS KB 329234)
-----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
2005 Jan 07
0
(Fwd) (Fwd) Re: second samba problem
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
2004 Oct 19
1
Issues/Questions about Samba 3.x.x versus it's Worki ng Status
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