similar to: INELT Monolith II 1000LT

Displaying 20 results from an estimated 130 matches similar to: "INELT Monolith II 1000LT"

2009 Jan 17
0
Megatec driver FR: repeat shutdown
Hello. In continuation to http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-June/002880.html Inelt Monolith II 1000 (don't know about LT) actually requires sending shutdown command twice, with delay of 5 to 8 seconds, according to my experiments. The attached patch enables the megatec driver to repeat shutdown command with configurable delay (cmdrepeat, in milliseconds). Default
2010 Oct 13
2
ups nut-2.4.x bug. driver megatec forceshutdown may dont work.
2010/10/13 Vitaly Lavrov > I found bug in nut/drivers/megatec.c - force shutdown may dont work. > See patch. > could you please give a try to blazer, since it is set to replace megatec with 2.6.0. Arjen will quite probably comment on your patch usefulness within the blazer scope. thanks for your contrib. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton -
2008 Feb 28
2
Unknown model detected - please report this ID: 'SOLA'
Some one might have answerd this, but I can not find any think yet I am trying to load a SOLA 610 700va ups up and keep getting : --------------------------------- Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.88 (2.0.5) .Detected Pulsar ESV11+ on /dev/cuaa0 Network UPS Tools - Best UPS driver 1.03 (2.0.5) Unknown model detected - please
2020 Jan 10
0
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Friday, 10 January 2020 15:05:33 CET Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.
2020 Jan 10
0
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Fri, Jan 10, 2020 at 02:05:33PM +0000, Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.
2020 Jan 10
0
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > Do you use the libvirt "secret" APIs at all (disk encryption, network > > disk auth passwords) ? If so you will need "libvirt-daemon-driver-secret" > > too. How about any other libvirt sub-driver APIs ? Networking ?
2020 Jan 10
0
[PATCH Fedora libguestfs v2] Don't depend on libvirt-daemon-kvm monolith.
libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec
2020 Jan 10
0
[PATCH Fedora libguestfs v4] Don't depend on libvirt-daemon-kvm monolith.
libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec
2020 Jan 10
1
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Friday, 10 January 2020 17:34:27 CET Daniel P. Berrangé wrote: > > > > virStoragePoolFree ( > > > > virStoragePoolGetInfo ( > > > > virStoragePoolLookupByName ( > > > > virStorageVolFree ( > > > > virStorageVolGetInfo ( > > > > virStorageVolGetPath ( > > > > virStorageVolLookupByName ( > > > > >
2020 Jan 10
0
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Fri, Jan 10, 2020 at 05:21:23PM +0100, Pino Toscano wrote: > On Friday, 10 January 2020 15:39:21 CET Daniel P. Berrangé wrote: > > On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > > > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > > > Do you use the libvirt "secret" APIs at all (disk encryption, network >
2020 Jan 10
1
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Fri, Jan 10, 2020 at 03:10:51PM +0100, Pino Toscano wrote: > On Friday, 10 January 2020 15:05:33 CET Richard W.M. Jones wrote: > > libguestfs usually needs qemu. However it only requires an emulator > > for the same architecture, not for all architectures. > > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > > architectures, as well as a bunch of
2006 May 08
1
How do I resolve comm issues
Hi, I'm running into an issue while using FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. The ups.conf is : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Telecom Closet Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3)
2020 Jan 10
2
Re: [PATCH Fedora libguestfs v2] Don't depend on libvirt-daemon-kvm monolith.
On Friday, 10 January 2020 15:59:35 CET Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.
2020 Jan 10
2
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > Do you use the libvirt "secret" APIs at all (disk encryption, network > disk auth passwords) ? If so you will need "libvirt-daemon-driver-secret" > too. How about any other libvirt sub-driver APIs ? Networking ? Host > dev, etc ? The full list of APIs we use is attached, assuming I got my
2020 Jan 10
2
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
On Friday, 10 January 2020 15:39:21 CET Daniel P. Berrangé wrote: > On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > > Do you use the libvirt "secret" APIs at all (disk encryption, network > > > disk auth passwords) ? If so you will need
2020 Jan 10
5
[PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. I also made support
2006 Jun 20
0
RE Network UPS Tools - ID string
Hi John, I've forwarded your info to the nut development list, and to Carlos who's in charge of the megatec driver. This one, which is only available in the subversion development tree, and soon in 2.0.4, will replace the fentonups driver. So you're encouraged to test it and report back. Arnaud Quette -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT)
2019 Mar 04
1
How to post a device dump to the DDL?
Hi!I have a device dump from my Inelt UPS. I want to post it in the Device Dump Library. But I can not figure out how to do it. Google also did not help me.Can anyone point me the right way?Yuri. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190304/55da7065/attachment.html>
2006 May 07
0
updateinfo and stale data
Hi, FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. I set the ups.conf up as : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3) Could not get multiplier table: using raw
2003 Aug 05
1
killing UUCP
Hey *, I'm getting an audit coming down the pipes and I have 2 4.6 release boxes to clean up. I say "clean up" because they have some requirements that I missed despite due diligence. My specific question is: To what extent can I get rid of UUCP? Aside from the SUID/SGID stuff that pops up via my finds, I simply see no reason to have any UUCP stuff on these boxes. Is this stuff