search for: fatalx

...um, i, ret; - char temp[256], model[32], *raw; + char temp[256], qmodel[32], *model, *raw = NULL; - raw = get_id(); + model = getval("model"); - if (!raw) - fatalx("Unable to detect a Fenton or Megatec protocol UPS"); + if (!model) { + raw = get_id(); - snprintf(temp, sizeof(temp), "%s", raw); + if (!raw) +...

...6,18 +206,21 @@ upsdebugx(2, "failed to claim USB device: %s", usb_strerror()); + if (retries-- > 1) { + continue; + } + + fatalx(EXIT_FAILURE, "Can't claim USB device [%04x:%04x]: %s", curDevice->VendorID, curDevice->ProductID, usb_strerror()); + } + + if (retries > 1) { if (usb_detach_kernel_driver_np(udev, 0) < 0) {...

...the regex mechanism */ int r; char *regex_array[5]; ^^^^^^^^^^^^^^^ => should be 6 /* enforce use of the "vendorid" option if "generic" is given */ if (testvar("generic") && getval("vendorid")==NULL) { fatalx("must specify \"vendorid\" when using \"generic\""); } /* process the UPS selection options */ regex_array[0] = getval("vendorid"); regex_array[1] = getval("productid"); regex_array[2] = getval("vendor");...

...if (blazer_instcmd("shutdown.stop", NULL) != STAT_INSTCMD_HANDLED) { continue; } if (blazer_instcmd("shutdown.return", NULL) != STAT_INSTCMD_HANDLED) { continue; } fatalx(EXIT_SUCCESS, "Shutting down in %d seconds", offdelay); } fatalx(EXIT_FAILURE, "Shutdown failed!"); } In order to support this flavor of protocol, a response "ACK" to a command should be considered valid. Regards, Alexander.

...===== Tripplite_usb.c 977,987d977 < /* Reset watchdog: */ < ret = send_cmd(w_msg, sizeof(w_msg), w_value, sizeof(w_value)-1); < if(ret <= 0) { < if(ret == -EPIPE) { < fatalx(EXIT_FAILURE, "Could not reset watchdog. Please check and" < "see if usbhid-ups(8) works with this UPS."); < } else { < upslogx(3, &quo...

...@@ void sec_poll ( int pollflag ) { void upsdrv_initinfo(void) { - int msglen, e, v; + int msglen, v; char *a,*p,avail_list[300]; /* find out which variables/commands this UPS supports */ @@ -264,7 +264,6 @@ void upsdrv_initinfo(void) if (strlen(avail_list) == 0){ fatalx(EXIT_FAILURE, "No available variables found!");} a = avail_list; - e = 0; while ((p = strtok(a, ",")) != NULL) { a = NULL; v = atoi(p); Index: b/drivers/isbmex.c =================================================================== --- a/drivers/isbmex.c 20...

...ut we couldn't > + * get an exact match, so opening instead. */ > + *mode = MODE_OPEN; > + } > + break; > + case 0: > upsdebugx(2, "Device does not match - skipping"); > goto next_device; > - } else if (ret==-1) { > - fatalx(EXIT_FAILURE, "matcher: %s", strerror(errno)); > - goto next_device; > - } else if (ret==-2) { > + case -1: > + fatal_with_errno(EXIT_FAILURE, "matcher"); > + default: > upsdebugx(2, "matcher: unspecified error"); > got...

On Aug 11, 2013, at 2:12 PM, ????????? ???????? wrote: > I see no problem with how the device communicates the Blazer/Megatec protocol. > I must have found a bug in the driver. It is possible that the shutdown was tested with a different implementation of the protocol. What do you get from the "I" command? On Aug 11, 2013, at 11:25 AM, ????????? ???????? wrote: > So I

...r@mail.telepac.pt> * * powermust.c created on 4/10/2003 * @@ -99,7 +99,7 @@ } QueryValues; -/* Defined in upsdrv_initups */ +/* Defined in upsdrv_initinfo */ static float battvolt_min; static float battvolt_max; @@ -206,13 +206,13 @@ } if (success < IDENT_MINSUCCESS) { - fatalx("Mustek PowerMust UPS, or compatible, not detected."); + fatalx("Megatec protocol UPS not detected."); } - upslogx(LOG_INFO, "Mustek PowerMust UPS, or compatible, detected."); + upslogx(LOG_INFO, "Megatec protocol UPS detected."); dstate_setinfo("...

Hello All, This is my first post to the list & I have tried to do as much searching and debugging on my own as I can bear. Please HELP! I am currently using up to date Centos 5.2 32-bit - kernel version: 2.6.18-92.1.10.el5PAE #1 SMP. I am using a Tripplite OMNIVS1500 via usb connection. I am using the tripplite_usb driver. I have tried to user versions 2.2.0 from an rpm, 2.2.2 & and the

Hello All, This is my first post to the list & I have tried to do as much searching and debugging on my own as I can bear. Please HELP! I am currently using up to date Centos 5.2 32-bit - kernel version: 2.6.18-92.1.10.el5PAE #1 SMP. I am using a Tripplite OMNIVS1500 via usb connection. I am using the tripplite_usb driver. I have tried to user versions 2.2.0 from an rpm, 2.2.2 & and the

I ran into a portability issue with drivers/bcmxcp.c in nut-2.4.1 on my UnixWare 7.1.4 machine. The error I get is ..... UX:acomp: ERROR: "/opt/src/utils/nut-2.4.1/drivers/bcmxcp.c", line 835: integral constant expression expected ..... Looking at the code we see ..... int init_outlet(unsigned char len) { unsigned char answer[len]; ..... Although gcc can handle it, it's not

Citeren Michal Soltys <msoltyspl-guest at alioth.debian.org>: > Log: > apcsmart: allow tearing down/setting up serial connection during > normal activity; If this is needed at all (why?), I don't think this should be handled at driver level, but this would need to be in the serial.c library. Opening/closing a serial port is independent from the protocol used (no data

On Dec 16, 2013, at 10:11 PM, David C. Rankin wrote: > On 12/16/2013 08:01 PM, Charles Lepple wrote: >> On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: >> >>>> Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >>>> ai_socktype >> [...] >>>> The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't

I have an old (1997) Best Ferrups (model FE18KVA) that I am trying to monitor for the first time, but all the Best drivers fail to communicate with it. In ups_sync() in bestuferrups.c and bestfcom.c, the "time" command is sent and a one-line response is read. However, on my UPS, that command returns the current time and then prompts for a new time setting. I worked around that by just

On 12/16/2013 08:01 PM, Charles Lepple wrote: > On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: > >> > Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >> > ai_socktype > [...] >> > The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't see what >> > could have changed. How do I attempt to further

...d. Removing this UPSD allows the custom value to be used correctly. Also I changed the shutdown messages so the ups.delay.* values are reported. With all that, here's what upsdrv_shutdown looks like: void upsdrv_shutdown(void) { if (upsc_commandlist()) { if (!can_upsd || !can_uppc) { fatalx(LOG_EMERG, "Shutdown called, but UPS does not support it"); } } else { upslogx(LOG_EMERG, "Can't determine if shutdown is supported, attempting anyway"); } upslogx(LOG_EMERG, "Emergency shutdown"); char msg[100]; snprintf(msg, 100, "UPS will reboot...

...ktype : %d\n", hints.ai_socktype); fprintf(stderr, "hints.ai_protocol : %d\n", hints.ai_protocol); if (v == EAI_SYSTEM) { fatal_with_errno(EXIT_FAILURE, "getaddrinfo"); } fatalx(EXIT_FAILURE, "getaddrinfo: %s", gai_strerror(v)); } I rebuilt nut and ran it, the error log contained: Dec 17 10:21:01 phoinix upsd[27151]: =========== Error Block Hit ============ Dec 17 10:21:01 phoinix upsd[27151]: getaddrinfo : Servname not supported for ai_s...

...NULL; > + hints.ai_canonname = NULL; > + hints.ai_next = NULL; > + > + if ((v = getaddrinfo(serv->addr, serv->port, &hints, &res))) { > + if (v == EAI_SYSTEM) > + fatal_with_errno("getaddrinfo"); > + > + fatalx("getaddrinfo: %s\n", gai_strerror(v)); > + } > + > + for (ai = res; ai != NULL; ai = ai->ai_next) { > + int sock_fd; > + > + if ((ai->ai_socktype != hints.ai_socktype) || (ai->ai_protocol != hints.ai_protocol)) > + continue; > + > + i...

...bdriver[mode]->initups() > 0) { upslogx(LOG_INFO, "CyberPower UPS with %s protocol on %s detected", subdriver[mode]->version, device_path); @@ -173,7 +173,7 @@ void upsdrv_initups(void) } ser_set_dtr(upsfd, 0); - usleep(10000); + nanosleep(&delay, NULL); } fatalx(EXIT_FAILURE, "CyberPower UPS not found on %s", device_path); Index: b/drivers/bestups.c =================================================================== --- a/drivers/bestups.c 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/bestups.c 2011-08-17 00:40:17.000000000 +0300 @@ -252,7 +2...