search for: quckly

https://bugs.freedesktop.org/show_bug.cgi?id=49736 Bug #: 49736 Summary: piglit quck.driver tests kill X server on nv43 Classification: Unclassified Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Mr Claesson, with my current configuration, the ups.status when the UPS is disconnected from the mains is "OB". There is no more "OB BOOST". Now my upsd.users is: [root] password = password allowfrom = localhost upsmon master actions = SET instcmds = ALL and upsmon.conf is: RUN_AS_USER root MONITOR Inform@localhost 1 root password master MINSUPPLIES 1 SHUTDOWNCMD

...t went via the GW had issues - if they weren't answered within a few milliseconds of ringing, then the call would fail - sometimes you'd get one way audio, sometimes none at all, and the GW or the CCM always sent a RELEASE within a few seconds, even if not answered. If you answered the call quckly, within ms of ringing, the call worked fine. Any other call (ie, that didn't use the PSTN gateway for outgoing calls) would work fine too, which was the most baffling. Even incoming via the PSTN gateway were fine. The chan_h323 in CVS and chan_oh323 both exhibited the same behaviour. I'd...

What is really puzzling me is that the ataraid device (/dev/ataraid/d0p1 mounted as /bigdisk) 2x 123GB IBM Deskstar's is formated as ext2...top and ps etc... show a fight between kjournald and kupdated and all searches for kjournald or kupdated fights suggest ext3 issues... :-) It's a RedHat 7.2, 2.4.7-10 custom kernal (I added in the Promise FastTrak support and HIGH mem support to

...you gave me below so thank you very > > much for that. > > > From what I can see this appears to me a memory allocation > > issue that > > > affects all systems but because the main node has such fast ethernet > > > speeds on can see the results of the problem quckly. I am > > testing this > > > problem on a system with more memory and may have a better > > sense of what > > > is needed once I see the results. > > > > > > I'll let you know as I learn more perhaps later today. > > > > > > Tha...

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/