search for: l295

...text=0x4182e834) [exception.c:250] in NTDLL.DLL) (ebp=4182e804) 4 0x400a9e47 (raise_segv_exception+0x2f(rec=0x4182eb00, context=0x4182e834) [signal_i386.c:853] in NTDLL.DLL) (ebp=4182e820) 5 0x400b1d7c (__wine_call_from_32_restore_regs [relay32.s] in NTDLL.DLL) (ebp=4182ebe4) 6 0x40b8957e (.L295+0x93 [tmarshal.c] in OLEAUT32.DLL) (ebp=4182ec30) 7 0x40b8933d (.L277+0x45 [tmarshal.c] in OLEAUT32.DLL) (ebp=4182ec8c) 8 0x40b8933d (.L277+0x45 [tmarshal.c] in OLEAUT32.DLL) (ebp=4182ece8) 9 0x40b8bb7a (TMStubImpl_Invoke+0x442(iface=0x40293600, xmsg=0x4182edcc, rpcchanbuf=0x0) [tmarshal.c:1...

CRAN, by relying on the powerful package management system that is part of R, provides an unparalleled framework for extending R with nearly 20k packages. We recently encountered an issue that highlights a missing element in the otherwise outstanding package management system. So we would like to start a discussion about enhancing its feature set. As shown below, a mechanism to force

When creating qcow2 images using virt-builder, is there a way to specify the qcow2 preallocation, as possible with qemu-img create -o preallocation=metada , for example? TIA, Y.

...ate -o > preallocation=metada , for example? No .. but .. it does default to preallocation=metadata provided that the output format is qcow2: https://github.com/libguestfs/libguestfs/blob/master/builder/builder.ml#L582-L585 https://github.com/libguestfs/libguestfs/blob/master/src/create.c#L281-L295 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http:/...

> https://github.com/networkupstools/nut/issues/138 > That issue also includes an override setting, so if I can't get any other testers, I plan to merge it as-is. Ok, great. > It should run as user "nut" in Debian. You may want to reinstall the nut-server package, and check the post-inst error messages to make sure that the "nut" user is created, and that it is

I currently do incremental backups using --link-dest. Unchanged files are hard links to the previous snapshot; changed files are new copies. Where this "fails" is for large files that have received small changes. The directory containing my main IMAP account, for example, typically generates between 1 and 2 G of daily backup data as I file messages in my inbox. Yesterday, though,

...parsed... > > What I should have said is that upsdrvctl is not where the "user = " is being interpreted (although you are correct, it is parsed and ignored). I was thinking of this line in the driver core: > > https://github.com/networkupstools/nut/blob/master/drivers/main.c#L295 > >> And the init script of the debian package don't explicitly append "-u nut" in wheezy. See the attached patch in my first message. > > Since we don't ship that init file in the generic NUT source package anymore, that will need to be discussed with the Debian...

Hi. I would like to share with you my experience on trying to use nut with a Liebert GXT3 on a Debian wheezy with nut-server 2.6.4. Please find my observations below. (1) I've installed the packaged version of nut-server # aptitude install nut-server (2) I did some tuning for my configuration #??cat << EOF >> /etc/nut/ups.conf user=nut [liebert] ??????? driver=usbhid-ups