search for: 0.000092

Displaying 10 results from an estimated 10 matches for "0.000092".

Did you mean: 0.000096
2007 Apr 04
0
Monit / mongel_cluster 0.2.2 / mongrel 1.0.1
Paul Did you ever get to the bottom of this. I''m having a similar (though possibly different) problem with a Rails app failing occasionally and on just one mongrel instance, which from the trace and behaviour seems to be ImageSceince/RubyInline related. See my post on Rails deployment group:
2007 Feb 02
1
Monit / mongel_cluster 0.2.2 / mongrel 1.0.1
Hi, I''ve a few problems with my rails app at the minute, causing mongrels in a cluster to die, while I debug I''ve setup monit to keep the site running. Problem is, whenever monit starts one of my mongrels via mongrel_rails cluster::start --only 8000 --clean -C /url/to/yml/file I get the following in my log/mongrel.log: ** Mongrel available at 127.0.0.1:8000 ** Writing PID file
2015 Jul 23
2
[Bug 2433] New: please add debug output when resolving
https://bugzilla.mindrot.org/show_bug.cgi?id=2433 Bug ID: 2433 Summary: please add debug output when resolving Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at
2023 Sep 23
1
Nut-upsdev Digest, Vol 206, Issue 5
Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??
2023 Sep 23
1
Nut-upsdev Digest, Vol 206, Issue 5
<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x
2023 Sep 19
1
Nut-upsdev Digest, Vol 206, Issue 5
Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your
2002 Jul 03
11
sync slowness. ext3 on VIA vt82c686b
When I copy a file(13Megs) from /home/ to /tmp/, sync takes almost 2 minutes. When I copy the same file to /usr/local/, sync returns almost right away. Both filesystems are ext3 and are on the same harddrive. When sync is running, the harddrive light stays on but I don't hear it doing anything. dmesg doesn't show any errors either. Below is the `time` output for each command. If you
2005 Nov 28
20
open/stat64 syscalls run faster on Xen VM than standard Linux
Dear all, When I debugged the execution performance of an application using strace, I found there are some system calls like open and stat64 which run faster on XenLinux than the standard Linux. The following is the output of running "strace -c /bin/sh -c /bin/echo foo" on both systems. An open call runs averagely 109 usec on standard Linux but only 41 usecs on XenLinux. An stat64
2009 Aug 13
9
[PATCHv2 01/10] drm/nouveau: Fix a lock up at NVSetOwner with nv11.
It seems it was only locking up in the context of nouveau_hw_save_vga_fonts, when it actually did something (because the console wasn't already in graphics mode). Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_hw.c | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_hw.c
2009 Aug 12
14
[PATCH 00/12] TV-out modesetting kernel patches.
This patch series adds TV-out modesetting support to the KMS implementation. I've tried to test it on all the hardware I've got at hand (that is nv11, nv17, nv34, nv35, nv40, nv4b) with every possible output combination; I believe it has reached a mergeable state, however it depends on some commits from drm-next that haven't got into Linus' tree yet, if you agree to merge this