similar to: 2.6.12-rc3-mm2 benchmarks

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, after upgrading to samba 3.0.8 (debian/unstable, i386) i too encounter similar problems as reported here: http://lists.samba.org/archive/samba/2004-November/095567.html upon logoff from a win2k(sp4) client, the profile cannot be saved and the samba logfile from the client (prinz) gives: [2004/11/26 17:57:06, 2]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [cc'ing 4 mailing lists, please reply to *one* list only!] hi, i was about to set up a new fs for my desktop machine and i could not decide which fs it should be. i've written a wrapper script for some benchmarks before, but it was not really good. i tried to rewrite it and so, here are the results: http://nerdbynature.de/bench/

I modified the CUPS access rights (defined in cupsd.conf). Before that only users of administrative group had access to the printer configuration parts. Now I removed all access restrictions, so that anyone can access all CUPS services (printers, jobs, ...) (we use this, because sometimes we need to hold printers manually ...). But, as I mentioned, I don't find the relationship between this

That was a good hint! Yes, I've installed SP2, and it realy seems to be the Problem. Now I've checked that on a machine with SP1 - and the jobs from the same printqueue are removed correctly there! -------- Original Message -------- Subject: Re: [Samba] Samba 3.0.9 doesn't remove printjobs ? (14-Dez-2004 19:13) From: novosirj@umdnj.edu To: t.pompe@architekt-prinz.at >

On Tue, 24 Jun 2003 ext3-users-request@redhat.com wrote : >Send Ext3-users mailing list submissions to > ext3-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/ext3-users >or, via email, send a message with subject or body 'help' to > ext3-users-request@redhat.com > >You can reach the person

hi, i've made *some* benchmarks, i plan to do more. benchmarks requests welcome, e.g. "please test this...with that.." https://ephigenie.kicks-ass.net/bench/benchmark.html but only in https://ephigenie.kicks-ass.net/bench/prinz are results right now. I hope this is helpful. Thanks, Christian.

On Tue, 14 Nov 2006 23:56:22 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Since people were recently complaining about too many warnings: > Here is a list of the warnings I'm getting in MODPOST and later. > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > I had to attach them compressed. > > With the exception of the

On Tue, 14 Nov 2006 23:56:22 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Since people were recently complaining about too many warnings: > Here is a list of the warnings I'm getting in MODPOST and later. > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > I had to attach them compressed. > > With the exception of the

i386 allmodconfig arch/i386/power/cpu.c: In function '__save_processor_state': arch/i386/power/cpu.c:29: warning: passing argument 1 of 'paravirt_ops.store_gdt' from incompatible pointer type arch/i386/power/cpu.c:30: warning: passing argument 1 of 'paravirt_ops.store_idt' from incompatible pointer type arch/i386/power/cpu.c: In function

i386 allmodconfig arch/i386/power/cpu.c: In function '__save_processor_state': arch/i386/power/cpu.c:29: warning: passing argument 1 of 'paravirt_ops.store_gdt' from incompatible pointer type arch/i386/power/cpu.c:30: warning: passing argument 1 of 'paravirt_ops.store_idt' from incompatible pointer type arch/i386/power/cpu.c: In function

Clean up of patch for letting kernel run other than ring 0: a. Add some comments about the SEGMENT_IS_*_CODE() macros. b. Add a USER_RPL macro. (Code was comparing a value to a mask in some places and to the magic number 3 in other places.) c. Add macros for table indicator field and use them. d. Change the entry.S tests for LDT stack segment to use the macros. Signed-off-by: Chuck Ebbert

Clean up of patch for letting kernel run other than ring 0: a. Add some comments about the SEGMENT_IS_*_CODE() macros. b. Add a USER_RPL macro. (Code was comparing a value to a mask in some places and to the magic number 3 in other places.) c. Add macros for table indicator field and use them. d. Change the entry.S tests for LDT stack segment to use the macros. Signed-off-by: Chuck Ebbert

Hello! I'm using samba with CUPS printing (with raw passthru) for a long time now and it worked very well. But after upgrading my samba installation from 3.0.2 to 3.0.9, the printjobs (sent from XP Workstations) aren't removed from the joblist anymore. Means: the job is printed correctly, but opening the printqueue on the XP machine still contains the job (not only mine, but jobs from

On Thu, 16 Nov 2006 00:16:26 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Paravirt breaks CONFIG_X86_PAE=y compilation: > > <-- snip --> > > ... > CC init/main.o > In file included from include2/asm/pgtable.h:245, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, > from >

On Thu, 16 Nov 2006 00:16:26 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Paravirt breaks CONFIG_X86_PAE=y compilation: > > <-- snip --> > > ... > CC init/main.o > In file included from include2/asm/pgtable.h:245, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, > from >

Hello all, I'm trying to set up my samba server rev 3.2.3 on opensuse 10.3 as a member of the active directory domain, so that client connections can be authenticated by the AD server. Unfortunately when I try to connect to the samba server from a windows XP system, it keeps on asking me for user name and password. I've been reading through various howto's and descriptions but no

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 [cc'ing 4 mailing lists, please reply to *one* list only!] hi, every now and then i'm running some benchmarks on filesystems i really use...here are the results: http://nerdbynature.de/bench/prinz64/2.6.14-rc2-mm2/bonnie.html http://nerdbynature.de/bench/prinz64/2.6.14-rc2-mm2/ may it be of some help.... thanks, Christian. PS:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, a good friend of mine had some trouble with his fs yesterday. i have some details now and wonder if you have some thoughts on it, even it may turn out not to be an ext3 issue at all. sorry, the post is a bit too long: the ext3 fs was running for several months now on a RAID controller. due to a user error, the RAID controller decided to rebuild

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, today i re-organized my data, lots of "mv" and "cp". then, upon unmounting a ext3 partition the following was shown on the console: (the leading "Mar 22 02:40:04 sheep kernel:" is cut here) - ------------------------------- ~ sb orphan head is 940994 ~ sb_info orphan list: ~ inode sdd4:940994 at cf852874: mode

http://fatooh.org/esfq-2.6/ http://fatooh.org/esfq-2.6/esfq-2.6.12-rc1.tar.gz This version no longer interferes with the original SFQ; unlike previous versions, you can still use an unpatched tc with SFQ. Patching tc is still needed for ESFQ, though. I''ve tested this patch with Linux 2.6.11 as well. Please tell me if you have any problems. I''m subscribed to lartc again. -Corey