similar to: [PATCH] disable nonblocking mode on serial port

Best fortress support was understandably dropped, but we still use them, and someone else may want the driver I ported to nut-2.0. We also often attach the serial cable from a UPS to a network terminal server, since servers these days don't come with very many serial ports. (They call them "legacy" ports.) I submitted a patch to support these for nut-1.x, and it was rejected

Hi! I'm new to this mailing list, so please help out if I'm adressing the wrong forum. :) I'm working on an application accessing a mounted networkshare. Under normal circumstances there is no problem accessing reading and writing to the networkshare using POSIX open(2)/read(2)/write(2) etc. However if there is intermittent connectivity problems to the networkshare my

Hello all, Some time ago, you all were very helpful in getting nut running on an OpenBSD system, using--for what it's worth--a CyberPower 1500AVR. So I finally got my FreeBSD system's UPS, also a CyberPower 1500AVR, within reach of its serial cable and I'm trying to get nut running here. I'm going nuts. Basically, I copied the OpenBSD configuration over to the FreeBSD system

Hola Estic fora de l?oficina des de Dimecres 1 d'Agost fins el proper Dilluns 12 d'Agost, Tan aviat sigui possible li contestar? el seu correu. En cas de ser un tema urgent, preguem reenvi? aquest mateix correu a l?adre?a d?email sst at salicru.com, els meus companys li donaran resposta el mes aviat possible, gr?cies. Hola Me encuentro fuera de la oficina del Miercoles 1 de Agosto

All, I just had a power failure that caused me a little drama. This spurred me into trying to get NUT up on my cyberpower 1500 again. For about 6 months I tried to get it to work with the new power panel drive with no luck. Today I removed all the old files for NUT and installed the newest version I could find (2.4.3) and it works perfectly now with my UPS. Hopefully now I

I''m almost afraid to ask because this probably sticks out like a sore thumb on the wiki somewhere, and I''m just not seeing it. But I have a bunch of files with the same owner/mode. Is there a way to somehow collapse these, so that all I repeat is the file name? Example: file { "/opt/test/1": owner => "jtan", group =>

This unit works fine with the "cyberpower" driver (which reports it as "Unknown model - 15"). It reads this much from it: battery.charge : 100 driver.name : cyberpower driver.parameter.pollinterval : 2 driver.parameter.port : /dev/ttyS0 driver.version : 2.2.0- driver.version.internal : 1.00 input.frequency : 60.2 input.voltage : 121 ups.firmware : 5.100

Is anyone working on anything to support the Cyberpower CP550SL/AE550 Serial? Any idea if it uses the same or similar protocol as the other Cyberpower models? I have an HP 4952A Serial Protocol Analyzer and a Cyberpower CP550SL. Once I get the CP550SL up and working in Windows over RS232 I'll hook up the 4952A and see whats going on. I'm not sure what it uses for default baud rate.

I have a CyberPower 1500AVR LCD connected by USB to an up-to-date Debian Testing box running nut 2.4.3. /etc/nut/ups.conf contains the following information: [myups] driver = usbhid-ups port = auto When I run upsdrvctl start I receive the following output: Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication

Hi, In an instance where the system is in a sometimes-unattended facility, are there different implications to shutting down the UPS from a script, as compared to not doing so? My goal is to have systems recover ASAP when the power comes back. My UPS is a Cyberpower 1500AVR. The two servers connected to it boot fine when power is restored to them. But I'm ignorant on how the UPS itself will

usleep is deprecated under POSIX 2008 and is optionally unavailable with uClibc-ng. Signed-off-by: Rosen Penev <rosenp at gmail.com> --- examples/nonblocking.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/examples/nonblocking.c b/examples/nonblocking.c index 8e38a94..2f15b80 100644 --- a/examples/nonblocking.c +++ b/examples/nonblocking.c @@ -70,8 +70,10 @@ int

I propose the following changes to the libshout API to support nonblocking I/O: New functions: int shout_set_nonblocking(shout_t *self, unsigned int nonblocking): Instructs libshout to use nonblocking I/O. Must be called before shout_open (no switching back and forth midstream at the moment). unsigned int shout_get_nonblocking(shout_t *self): self-explanatory. Changed functions:

Hello, I found a bug in Icecast-2.3.2. SVN trunk is affected either. The problem lies in src/net/sock.c: sock_connected() function. This function is used to check status of socket after nonblocking connect(2) and it has two implementations: select(2) and poll(2). The select branch does the right job---it gets socket status by getsockopt(2) after selecting for write. But the poll branch does not.

Hi Ara, I''ll take a look. In the meantime, I''ve cc''d the win32utils-devel mailing list to see if anyone has any ideas/suggestions. Regards, Dan > -----Original Message----- > From: ara.t.howard at noaa.gov [mailto:ara.t.howard at noaa.gov] > Sent: Wednesday, November 01, 2006 12:36 PM > To: Berger, Daniel > Subject: fatal flaw in popen4 on windows?

> Case in point; EAGAIN can come if you give your fd to another process > and continue using it yourself. > Short counts; It is documented behavior that read() and write() may > return short counts. It is not documented why, so you can not make > any assumptions. You might be right about short counts but if you're right about EAGAIN, there are bugs everywhere. My first

Hi! Trying to set up NUT on Centos 5 to monitor a CyberPower 1500AVR UPS. There seem to be many documents, all of which seem to be not fully consistent with each other, and most of them aren't up to date. I'm guessing I should be using udev rather than hal, but I'm somewhat stumped on how to figure out what device it should be monitoring. there are a bunch of udev rules installed

https://bugzilla.mindrot.org/show_bug.cgi?id=1467 Summary: SFTP stalls Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Other OS/Version: Other Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy: sconeu

The quick summary is that we invoke git from a parallel invocation of "make". Git invokes ssh to pull stuff from a remote repo. Ssh sets O_NONBLOCK on stdout and stderr if they do not refer to a tty. During our build, stderr refers to a pipe that other jobs run by make (and make itself) may also write to, and since this is a parallel build, they may write to that pipe while ssh has it

I wrote a small program to monitor keyboards found on /dev/input/event* It works great but I always get EAGAIN from my read() function. google says this is normal when open() is used and O_NONBLOCK mode. I know this is slightly offtopic but I was wondering if the centos gurus that also program know anything about this. My goal was to not be eating CPU cycles with a small program that just

Hi Brian, I've added the nut user list as this kind of info might be helpful to others. > I've got a Cyberpower 1500AVR UPS and it works great with my FreeBSD > 6.0 server using NUT and the serial cable. However, my server only has one > serial port and I would like to use it for a console connection. My UPS > did come with a serial to USB converter and it would be ideal if I