similar to: [PATCH] upsstatus += HB, TEST

On Tue, Jan 27, 2009 at 04:39:13PM +0100, Arnaud Quette wrote: > Hi Kirill, > > 2009/1/27 Kirill Smelkov <kirr at mns.spb.ru> > > > On Tue, Jan 13, 2009 at 05:58:23PM +0300, Kirill Smelkov wrote: > > > Arjen, Arnaud, > > > first of all, I'm sorry for my late reply. > > > > > > If it's not too late, here is updated al175: >

Hello up there! Attached is my patch to add support for AL175 alarm module, Please ACK or NAK this. -- ?????? ??????? -------------- next part -------------- A non-text attachment was scrubbed... Name: al175.patch Type: text/x-diff Size: 35632 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20050919/84b639e0/al175-0001.bin

Hi Kirill, just to notify you that your al175 driver is being removed from the NUT tree, as of 2.4.0-pre1. if you wish to see it entering the tree again, please contact the Development mailing list to talk about it. Merry Christmas and happy New Year. Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader -

Release Announcements ===================== This is the first release candidate of Samba 3.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.5.0 include: General changes: o Add support for full Windows timestamp resolution

Release Announcements ===================== This is the first release candidate of Samba 3.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.5.0 include: General changes: o Add support for full Windows timestamp resolution

Citeren Kirill Smelkov <kirr at mns.spb.ru>: > So what would we do about this patch? It fails to address the concerns raised, so we have no other option than to reject it. > I've tried to address the issues you've raised, and to describe my > rationale behind alarm(). The use of alarm() here is inappropriate (and possibly incorrect as well, see below). As stated

Peter, Thanks a lot for your latest changes to newhidups, which I like a lot. Unfortunately, when I tried to build the latest development tree stuff, I got a compile time error when compiling al175.c. It looks to me like my compiler, gcc-3.4.4-2.fc3, doesn't like the macro definition for "RECV(reg) do" because of a poorly inserted comment. I fixed the problem locally by the

Here's the problem in a nutshell: One samba-server (stand alone) A couple of Windows XP (sp2) clients All connected through a gigabit network Transfers between two of the windows computers works just fine and the speed is about 20-30MB/s. Transfers from the server to any windows computer also works fine and has the same speed. Transfers TO the server from any windows computer is horribly

On Nov 18, 2013, at 11:53 AM, Kirill Smelkov wrote: > Please find main description in github issue tracker > > https://github.com/networkupstools/nut/issues/69 > > and, for completness, both patches attached to this mail. This is now part of the 2.7.1 release. Regards, -- Charles Lepple clepple at gmail

Release Announcements ===================== This is the third release candidate of Samba 3.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.5.0 include: General changes: o Add support for full Windows timestamp resolution o

Release Announcements ===================== This is the third release candidate of Samba 3.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.5.0 include: General changes: o Add support for full Windows timestamp resolution o

lower your debug level. High debug level lowers performance... Mit freundlichem Gru?, Dirk Laurenz Systems Engineer Fujitsu Siemens Computers Sales Central Europe Deutschland Professional Service Organisation Nord / Ost Hildesheimer Strasse 25 30880 Laatzen Germany Telephone: +49 (511) 84 89 - 18 08 Telefax: +49 (511) 84 89 - 25 18 08 Mobile: +49 (170) 22 10 781 Email:

Hi, in FreeBSD kernel is options that make router stealth, packet passed throw router have no change in TTL value. Is a posibility to make similar thing in Linux, I think that in traceroute isn''t this hop, no asteris, no router, no change in TTL, nothing ...? PSIkappa psi@atlantis.sk

You guys are my last resort... When i do ip rule add/ls/del i get this message: RTNETLINK answers: Invalid argument I use 2.4.0 kernel with ip:adv. route, and pol. routing compiled in.

Release Announcements ===================== This is the second release candidate of Samba 3.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.5.0 include: General changes: o Add support for full Windows timestamp resolution o

Release Announcements ===================== This is the second release candidate of Samba 3.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.5.0 include: General changes: o Add support for full Windows timestamp resolution o

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

Thanks for the insights, especially these: > If this is about having variables with thresholds that control devices or cause synthetic setting of some variable (like turning on LB if charge% is < battery.charge.low), then it makes sense. > "battery voltage is unreasonably high" is a reasonable concept. <...> I would not call it HB, though because that makes it sound

Kicking the old tyre a bit once more: In my recent reading I saw "float charge", "float mode", "float voltage" etc. Maybe that is what I meant in the earlier discussion - similar concept, similar word. In case of PbAc per https://chargetek.com/basic-information.html : "Float mode is where the voltage on the battery is maintained at approximately 2.25 volts

Jim Klimov <jimklimov+nut at gmail.com> writes: >> "battery voltage is unreasonably high" is a reasonable concept. <...> I >> would not call it HB, though because that makes it sound parallel to LB, >> which is about believed remaining capacity, not detection of overcharging >> failure. > > Well, given that a "battery.charge.high" is