similar to: 2.2.2 printing.

Hello, I now added the following options to my smb.conf file: disable spoolss = 1 use client driver = 1 According to the file Whatsnew.txt in the source distribution this revert the printing behaviour back to 2.0. Now things seem to work (including queue manipulation). Regards, Michel > Hello, > > I am using RH 7.1 with CUPS and a printer connected to it. I also have > a windows

>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

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

Hi again, The PGP sig for 2.2.2 is missing from http://eu1.networkupstools.org/source/2.2/ (so the corresponding link from the download page is broken). Also, for the record, I'm trying to compile 2.2.2 from sources and so far, on my Ubuntu Hardy system : - If I don't use during configure "--without-snmp", compilation crashes talking about some undefined things. - If I use

>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.

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

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:

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 RPMs should install fine on F-15, and you can always rebuild with > rpmbuild.

was trying to match different matrices of different lengths with in the first collumn date and time info (yearmonthdayhourminute). the routine needs to return NA?s where data of either of the matrices is non existent. have been trying the following: #### x <- c(200112030003, 200112030004, 200112030005, 200112030006) y <- c(0.1, 1, 1.1, 1.5) a <- c(200112030004, 200112030005,

http://bugs.freedesktop.org/show_bug.cgi?id=23231 Summary: Nouveau driver from git fails to build Product: xorg Version: 6.99.99.904 (7.0 RC4) Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: high Component: Driver/nouveau AssignedTo: nouveau at

Hello, I'm updating Fedora's LLVM to the latest 2.6 prerelease, and experiencing test failures on ppc. On x86_64 and x86_32 all tests pass as expected. http://koji.fedoraproject.org/koji/taskinfo?taskID=1660661 (see root.log to see what packages are installed for the build, and build.log for the build log -- 'make check' is called towards the end. Thanks, -- Michel Alexandre

Setup: samba 2.2.2 Solaris 8 Trying to print to a printer attached to an NT4/sp6a machine. Printer passes 'test print page' test on NT and is shared. Problem: An error occurs when the smbclient command is used: cat afile | smbclient \\\\tech223\\testprn -U username%password -P -c "translate;print -" The error reported is "ERRDOS - ERRbadaccess (Invalid open mode.)

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

Hi there. I'm running Samba 2.2.2 on a Red Hat 7.2 system. I've set up a few disk shares (with the writable option set to yes), but I can't write to them. I can read from them ok, so I don't know what the problem is. I'm trying to write to the shares from a Windows 2000 Professional computer. Here's a part of my logs that appear every time I try to write to a share:

Ok, I've managed to print to my HPDeskjet 694c attached to a Solaris 8 box running samba 2.2.2 from Win98. Problem is with the left margin, there are these little lines (garbage) running down the 1st column on the left side of the page. Also, when I print a page from Word 97, the whole page doesn't print (about 95% of it) and starts a little too far down the page. Printing was perfect

Hi, I just install 2.2.2 in a Red Hat 7.2 with kernel 2.4.16 on ext 3 + lvm. The problem are the locks!!!!!! I've 5 users working in .dbf + cdx (foxpro) files with an 16 bits application. It accesses to the files via DAO 2.0. A lot of times in the days the users gets 'currently locked' messages when the application open the dbf's files with read only access! I desactivated the

Hi again, I tested several times using the Megatec driver from nut 2.2.2 to no avail, as it definitely never "sees" the UPS. Always getting : # drivers/megatec -DDD -a Alpha Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec] Carlos Rodrigues (c) 2003-2008 debug level is '3' Starting UPS detection process... Asking for UPS status [Q1]... Q1 => FAILED

Network UPS Tools version 2.2.2-pre2 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.2-pre2.tar.gz - News: http://www.networkupstools.org/source/2.2/testing/new-2.2.2-pre2.txt - ChangeLog: http://www.networkupstools.org/source/2.2/testing/ChangeLog Arnaud and the NUT team -- Linux / Unix Expert R&D -

Hi, When defining a queue for lpd using a SMB (Win95) printer, it uses a ".config" file that store a username and password for printing on the SMB server. Is there a way (as anybody tried and how to) to configure the lpd so the username and password used to print on the SMB server are the unix login and password of the user printing (password databases are synchronized), so the job on

Greets; This centos6.2 system seems to have python-2.6.6, but that is turning into a huge problem because I now have a backlog of about 40 packages that will not upgrade because they all need python 2.4. That, and importing gpg keys doesn't seem to be helping in that regard. But first, how to go about down grading python to 2.4? Thanks. Cheers, Gene -- "There are four boxes to be