similar to: APC Smart-UPS X 1500 Restart Issue.

Hello All I am trying to use nfs4acl_xattr plugin from samba source code. https://www.samba.org/samba/docs/current/man-html/vfs_nfs4acl_xattr.8.html I mounted NFSv4 mount point locally and exported it through samba with vfs objects set to nfs4acl_xattr. *[root at test3 ajain]# net conf showshare local[local] path = /home/ajain/mount comment = local share guest ok =

http://bugzilla.mindrot.org/show_bug.cgi?id=1264 Summary: Channel not close by sshd Server Product: Portable OpenSSH Version: 4.3p2 Platform: Other OS/Version: HP-UX Status: NEW Severity: critical Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org ReportedBy: ajain at hp.com

On Fri, Apr 06, 2018 at 12:40:31PM -0700, Jeremy Allison wrote: > On Fri, Apr 06, 2018 at 09:22:17PM +0200, Ralph Böhme wrote: > > On Fri, Apr 06, 2018 at 10:27:32AM -0700, Jeremy Allison via samba wrote: > > > On Fri, Apr 06, 2018 at 01:44:50PM +0530, Akash Jain wrote: > > > > Hi All > > > > > > > > I found there is one bug in the plugin. The

Hello, I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've got the message : "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" I've been looking for "pollonly" in the usbhid-ups man page, but it didn't help me. Could someone explain me what does this means exactly ? What are

tisdagen den 16 december 2014 15.36.29 skrev Frantz de Germain: > Hello, Hi Frantz, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. > I've got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of > this message)" > > I've been looking for "pollonly" in

Hello, Yes, "pollonly" is a driver option for certain devices (and relevant to just some drivers). Disconnects are probably relevant, at least to loss of connection (and staying that way, with less agressive retries in NUT v2.7.4 and before). There is a logged issue that "pollonly" mode might have trouble detecting a disconnection/staleness, I'm not sure there's merit

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto

Hello R-helpers, I have a list that only contains dataframes. Each element of the list (i.e., each dataframe) has a unique name ("one" through "ten"). I wish to add a new column (called "NAME") to each list element (i.e each datarame) and I want that column to contain the name of it's list element. e.g. the list element (i.e., dataframe) called "one"

Hi Guys, I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs. The current usbhid-ups driver recognises APC UPSs by the Vendor ID and Product ID of 0x051D and 0x0002. This needs to be amended with the new Product ID of 0x0003. (See attached file: apc-hid.patch) Secondly, when Nut polls the UPS via the interrupt channel, these will time out, resulting in frequent lost

Hi all, Have been using Nut on Linux for over ten years now and find it brilliant. Thanks. Just upgraded to 2.4.2 and have the 5 or 6 models of UPS's that we use (apcsmart, megatec, mge-shut, surgemax, digitus) all working including the MGE Pulsar Evolution 1100 on a USB connection using the usbhid-ups driver. Running on SLES9. Old but we still have a few servers out there running

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Linux NUT 2.7.1 Eaton 5PX usbhid-ups It would appear that interrupts are not actually working on my 5PX using the usbhid-ups driver. I will be trying the serial mge-shut driver next. It just seemed like it was working before because of the default pollinterval of 2 seconds. The status update comes in during the pollinterval no matter what I have pollfreq set to. And I can set pollonly and

Hello Jeremy and Ralph Thanks for your suggestions. I compiled samba-4.8.0 and running it instead of samba-4.6.2. I saw the changes that you mentioned in the latest vfs_nfs4acl_xattr module. The operation not supported error is gone but it is now failing with access denied. Here is what I tried: *[root at test3 ajain]# net conf showshare local[local] path = /home/ajain/mount

Hello, On one hand, sorry to hear that higher polling frequency in upsmon did not help. On another, question is if the driver gets the info (online state and its changes) from device quickly enough. Initially I meant for you to also try if the "pollonly" flag (in each device section of ups.conf for usbhid-ups instances) would make a difference?.. I'd expect data-transfer interrupts

Hi all, I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB (didn't try serial yet). UPS should work via HID driver but ups.status is not rendered properly. Specification of UPS says USB HID compatible. HID driver is the only one which talks with UPS as i try a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is

Sergey, I?m no expert on this but I have been reading the driver code, trying to sort out bigger problems with the OpenUPS driver! I can make 2 observations that I can?t check out myself : ?beeper.disable? was previously ?beeper off? - and ?beeper.enable? was ?beeper.on?. Not sure if it?s worth trying the old versions? If your UPS doesn?t wait for LB, could this be because there is another

I want to revive an old discussion. Should we use the contents of input reports or not? A while back, we decided not to use the contents of input reports, because there is no guarantee that input report 'n' has the same meaning as feature report 'n'. We have not seen any cases so far where this is not the case, but as far as we could see, there is nothing in the HID PDC

On Wed, 18 Oct 2017, Drew Plaster wrote: > MASTER SYSTEM > > nut.conf > MODE=netserver > > ups.conf > [TOPAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309002707" > desc = "TOPAPC" > [MIDAPC] > driver = usbhid-ups > port = auto > pollonly > serial =

On 6/19/23 20:29, gene heskett wrote: Some speeling korrections > On 6/19/23 18:57, gene heskett wrote: >> Greetings Jim & friends; >> >> Just installed nut 2.7.4 on a debian bullseye system.? ups is: >> Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS >> Device Descriptor: >> ?? bLength??????????????? 18 >> ?? bDescriptorType????????

Hi Philip, I've updated NUT to 2.7.3 and finally found the root cause for the unexpected shutdown: It is recommended to increase pollinterval to 10 seconds in ups.conf for usbhid-ups driver due to a known issue: http://www.networkupstools.org/docs/man/usbhid-ups.html Default DEADTIME=15 in upsmon.conf was triggering shutdown. Increasing the value to 30 seconds resolved the issue. Now when