search for: tedm

On 4/12/06, Ted Mittelstaedt <tedm@toybox.placo.com> wrote: > > >-----Original Message----- > >From: Ted Mittelstaedt [mailto:tedm@toybox.placo.com] > >Sent: Tuesday, April 11, 2006 6:04 PM > >To: Nikolas Britton > >Cc: Harrison Peter CSA BIRKENHEAD; freebsd-questions@freebsd.org > >Subject:...

...out netdb.h Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org ReportedBy: tedm at toybox.placo.com System is Sparc running Solaris 2.5.1 when typing "make" I get the following error on just about every single .c file compiled, here is a sample: In file included from includes.h:54, from authfd.c:37: /usr/include/netdb.h:195: warning: `struct sock...

...operly Product: Portable OpenSSH Version: 3.6.1p2 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org ReportedBy: tedm at toybox.placo.com The target system is a Sun Sparc 5, running Solaris 2.5.1 with all the OS patches. OpenSSL version 0.9.7b is installed and passed all tests. Perl version 5.8.0 is installed. Note that Solaris 2.5.1 does not come with openSSL installed, so the openssl include files are NOT pr...

Hello Ted, 2013/9/11 Ted Mittelstaedt <tedm at mittelstaedt.us> > Hi All, > > About a month ago APC announced they were including MODBUS protocol > support in their new APC UPSes. The technical note on this is here: > > http://www.apcmedia.com/**salestools/MPAO-98KJ7F/MPAO-**98KJ7F_R0_EN.pdf<http://www.apcmedia.co...

On 7/9/2014 4:16 PM, Charles Lepple wrote: > On Jul 9, 2014, at 11:24 AM, Ted Mittelstaedt<tedm at mittelstaedt.us> > wrote: > >> Someone could write a driver for MODBUS for NUT, all of the >> information and materials are available to do it. The simple fact >> of it is that the reason no one has done so is that the apcupsd >> program is available. > >...

Hi All, About a month ago APC announced they were including MODBUS protocol support in their new APC UPSes. The technical note on this is here: http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf "Application Note #176 Modbus Implementation in APC Smart-UPS" The APC "announcement" appeared on their site in their user blogs by an APC employee, here:

On Nov 7, 2014, at 11:47 AM, Ted Mittelstaedt <tedm at mittelstaedt.us> wrote: > Now I suppose your going to respond with that immature drivel that's been floating around, lets see if I remember it: > >> Because it messes up the order in which people normally read text. >> > Why is top-posting such a bad thing? >&...

On Jul 9, 2014, at 11:24 AM, Ted Mittelstaedt <tedm at mittelstaedt.us> wrote: > Someone could write a driver for MODBUS for NUT, all of the information > and materials are available to do it. The simple fact of it is that the > reason no one has done so is that the apcupsd program is available. You're right, it's the microlin...

Hi Ted there was a drift from the initial topic. worth a new thread! 2014-07-27 9:13 GMT+02:00 Ted Mittelstaedt <tedm at mittelstaedt.us>: > On 7/26/2014 12:18 PM, Arnaud Quette wrote: > >> Hi Eric, >> >> sorry for the lag, summer time... >> >> I'm first seconding Charles comments >> >> 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr at thyrsus.com >&gt...

On 7/9/2014 6:51 AM, Charles Lepple wrote: > On Jul 9, 2014, at 6:31 AM, Eric S. Raymond<esr at thyrsus.com> wrote: > >> What I'd like to do is this: confer in real-time, perhaps via IRC, >> with someone who knows this process. Ask about every step >> (thought processes and diagnostics). *Write them down* and turn >> this into a document on how to qualify

http://bugzilla.mindrot.org/show_bug.cgi?id=565 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #304 is|0 |1 obsolete| | ------- Additional Comments From djm at mindrot.org 2003-05-26 11:04 ------- (From

Here is the general procedure to do this: First, you must compile nut yourself on ubuntu, with the patch, then rename the existing NUT binaries to backup files and copy over your modified binaries to where the original binaries were. However, since these patches are local, if the nut package maintainer for Ubuntu releases a new package, your patches will be overwritten. To fix this, after you

Hello, i write because i have a doubt. I installed on an ubuntu server 12.04 64 bits the service nut with the command apt-get install nut. I configured nut and all is running fine except the shutdown the ups. I find a driver patch (source code) and it solves my problem. This i probe in a virtual machine with the same ubuntu, i compile and do the tests. My question is how i change in the production

On 11/3/2014 9:25 PM, thomas schorpp wrote: > Hi Ted, > > Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >> > >> Note that since the UPS relies on the voltage from the battery pack to >> determine state of charge, it is quite useful to add in the battery pack >> voltage to the logs as such: >> >> --- upslog.c.orig 2012-07-31 10:38:58.000000000

Now hold on there... you said the problem started when you updated kernels - not when you changed the config file - did you change the config file or was it wrong before and the old kernel accepted it anyway? ted On 12/17/2013 10:08 AM, David C. Rankin wrote: > On 12/17/2013 10:43 AM, David C. Rankin wrote: >> Huh? Why the : in Servname? So I just hardwired it passing the port

On 6/2/2014 6:28 AM, Charles Lepple wrote: > On Jun 2, 2014, at 7:27 AM, elliot smith wrote: > >> For example I am using FreeNAS. Rather than supporting my unorthodox UPS >> signaling scheme by installing it as a script in FreeNAS, (and me probably >> messing something up in the process) this scheme could be supported >> instead by NUT. > > Bear in mind that

Hi All, I put my Compaq R3000 UPS on NUT. Every once in a while the battery alarm light turns on, on the front of the UPS. Maybe once every couple of days or so. When that happens I get the following output in /var/log/messages: Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: .20 MOUL1 Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: 0119.20 MOIL1 Sep 22

On 11/8/2014 6:54 AM, thomas schorpp wrote: > Dear Ted, > > Am 07.11.2014 um 17:47 schrieb Ted Mittelstaedt: >> On 11/3/2014 9:25 PM, thomas schorpp wrote: >>> Hi Ted, >>> >>> Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >>>> >>> >>>> Note that since the UPS relies on the voltage from the battery pack to

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>

My personal experience with a number of UPSes that are monitored via USB cable is that communications errors such as the ones referenced in the issue you linked to below are a result of USB hardware incompatibilities between the USB chipset and the USB port on the motherboard.*? This is NOT specific to the NUT project as it affects both apcupsd and in fact, has been reported as an issue with