similar to: [nut-commits] svn commit r1285 - in trunk: . common include

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o

Description: Fix warning: variable set but not used [-Wunused-but-set-variable]. bugs.debian.org/633756. Related drivers were not tested. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index: b/drivers/belkinunv.c =================================================================== --- a/drivers/belkinunv.c 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/belkinunv.c

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:

In order to improve the diagnostics for serial connected devices, I would like to add the possibility to differentiate between errors and timeouts. For the ser_get_char() and ser_get_buf_len() we might do this by changing the return value. For the first, return value -1 would be an error, 0 a timeout and 1 success. The latter could return -1 on error, between 0 and (buflen-1) for a

Hi Tomas, Thanks for your prompt reply and your offer to help. I might need to get back to this since I am not too experienced in debugging these kinds of issues. Anyway, I gave it a try and I think I have found the immediate cause: I installed the debug symbols (r-base-core-dbg), placed https://github.com/wch/r-source/blob/tags/R-3-5-2/src/library/parallel/src/fork.c in cwd and changed the

Hi all, With the help of Tomas, I was able to track the issue down: Prior to R v3.6.0 the parallel package passes an uninitialized variable as the file descriptor argument to the close system call. In my particular R session this uninitialized variable (reproducibly) was holding the value 7, which corresponded to the file descriptor of the write end of the pipe the second child would use to

Hi all, With the help of Tomas, I was able to track the issue down: Prior to R v3.6.0 the parallel package passes an uninitialized variable as the file descriptor argument to the close system call. In my particular R session this uninitialized variable (reproducibly) was holding the value 7, which corresponded to the file descriptor of the write end of the pipe the second child would use to

Hi Andreas, thank you very much, good job finding it was EBADF. Now the question is why the pipe has been closed prematurely; it could be accidentally by R (a race condition in the cleanup code in fork.c) or possibly by some other code running in the same process (maybe the R program itself or some other code it runs). Maybe we can take this off the list and come back when we know the cause

I am determined to see wine work again on Solaris. A while back there was some discussion on a modification of mmap to allow dos mode to work. The thread of wine-develop faded out after a while with no resolution. Can someone outline this problem and how it affects wine, and give me some reason why the finally proposed solution from last year should not be applied This was the last reference I

On Tue, 8 Sep 2015 22:25:54 -0400 Charles Lepple <clepple at gmail.com> wrote: > @rpvelloso on Github suggested some changes (driver version v0.64) > that should help with the initial sync: > > https://github.com/networkupstools/nut/commit/debc8e0280ea4de9a0db5ca34aa66705b285f61f > > It's the solis_debug branch on Github. > > Does that help? I'm concerned

On Sun, 23 Aug 2015 11:09:03 -0400 Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > > > >> Not sure what to look for yet. It might be easier to add in the > >> debug calls to the source code-- can you try building NUT from > >> source? If you installed via the ports tree (as

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

Inital tests with two apc units (2005 and pre-2000) seem to go well. See commit message for details. I'll add more detailed rationale after getting some sleep :) Michal Soltys (1): apcsmart: switch processing to ICANON + minor fixes drivers/apcsmart.c | 270 +++++++++++++++++++++++++++++++++++----------------- drivers/apcsmart.h | 127 ++++++++++++++++--------- 2 files changed, 267

Hi, my UPS is a Best Fortress LI1420 with the monitoring master running fedora 7. I have to replace the manufacturer's software "Checkups II" because it's not working with releases after fc4. My choice is the nut package. But it isn't just installing rpm's and configure the parameter files. ? The first hurdle to take was realising the UPS doesn't send a prompt.

Hi Michal, I've cc'ed -upsdev, since some info could be interesting for everybody. 2011/5/27 Michal Soltys <soltys at ziu.info> > On 11-05-25 09:35, Arnaud Quette wrote: > > Hi Michal, > > > > 2011/5/25 Michal Soltys <soltys at ziu.info <mailto:soltys at ziu.info>> > >(...) > > > > I'm preparing larger patchset with

On Jan 19, 2016, at 9:37 AM, Ben Kamen <ben at benkamen.net> wrote: > > Hey there, > > I got a new UPS (CyberPower PR1500LCDRTXL2Ua) and found the serial drivers don't quite work... [...] > Essentially, I rewrote powpan_status so it better tolerates strings of different lengths (although I only have the 1 UPS right now, so I can't test against another and different

Some UPSes contain HID report descriptors that fail to correctly describe the contents of reports. For example, the OpenUPS descriptor fails to set the units, logical maximum and logical minimum before the corresponding `main item' as required by the HID specification. This commit allows an override HID report descriptor to be given to usbhid-ups which replaces the one produced by the UPS,

The 2.0.2+ tripplitesu drivers do not recognize SmartOnLine SU2200XL and possibly other SmartOnLine UPSes. Here is a one-line fix. Lee --- ../nut-2.0.2/drivers/tripplitesu.c Thu Jan 27 08:33:21 2005 +++ drivers/tripplitesu.c Sat Oct 1 13:38:51 2005 @@ -227,7 +227,7 @@ buffer[4] = '\0'; if (!strcmp(buffer, "~00D")) { - if (ser_get_buf_len(upsfd, buffer, 4, 3, 0) <=

I am having a problem with smbsh. I get the following error after I enter my username and password: ERROR: can't get smbw shared lock (Invalid argument) I am running linux 7.2 with samba 2.2.2. The error message is produced from the function lockit(void) in smbwrapper/shared.c. The error originates in file lib/util.c in function: fcntl_lock(shared_fd,SMB_F_SETLKW,0,1,F_WRLCK) fcntl_lock

Hi Andreas, the error is reported when some child process cannot send results to the master process, which originates from an error returned by write() - when write() returns -1 or 0. The logic around the writing has not changed since R 3.5.2. It should not be related to the printing in the child, only to returning the value. The problem may be originating from the execution environment,