similar to: tripplite_usb

hi All, Ubuntu 12.04 and glusterfs 3.3.1. root at tipper:/data# df -h /data Filesystem Size Used Avail Use% Mounted on tipper:/data 2.0T 407G 1.6T 20% /data root at tipper:/data# du -sh . 10G . root at tipper:/data# du -sh /data 13G /data It's quite confused. I also tried to free up the space by stopping the machine (actually LXC VM) with no lock. After umounting the space

We upgraded our Internet server to CentOS 5 from RedHat 4. Now we can't use the USB port. dmesg returns: usbcore: deregistering driver usb-storage Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:07.2 (0000 -> 0001) PCI: No IRQ known for

I have this: mount -t smbfs -o username=rharris,rw,uid=rharris,gid=500,fmask=640,dmask=750 \ //fileserver.lsv.raindance.com/departments +/wmnt/fileserver/departments (all on one line though, the backslash in for readability) When I run that I get this: INFO: Debug class all level = 2 (pid 24219 from pid 24219) can't determine netmask for 127. added interface ip=10.10.117.230

For those of you running SuSE 9.1, I do not recommend upgrading to 9.2 at this time. Refer to http://shorewall.net/myfiles.htm for information on my configuration: a) On Ursa: 1) After the upgrade, both of the NICs were recognized as "configured" in YAST yet neither of them would start; ifup claimed that no configuration could be found for either interface. Only got them running

Hi: I really liked the music on your 32kbps stream. That is what I listened to. It is very high quality low bandwidth. You must have a recording studio as well as the station. The website for the Linux Public Broadcasting Network is www.lpbn.org I'll create a mailing list for radio on LPBN later tonight so our emails don't disrupte the kind folks at icecast. Just a note, on Sunday I

Hi, I have a simple question on interpreting output results from your msm package in R when using a categorical model with hcovariates i.e. covariates on the parameters of the emission model. The interpretation is straightforward for normal distributions, etc. but when using categorical distributions I get results like these: prob P(1)

hi All, # gluster volume info data Volume Name: data Type: Distribute Volume ID: d74ab958-1599-4e82-9358-1eea282d4025 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: tipper:/mnt/brick1 Options Reconfigured: nfs.export-dirs: on nfs.export-volumes: off nfs.export-dir: /install nfs.port: 2049 nfs.ports-insecure: off nfs.disable: off nfs.mount-udp: on nfs.addr-namelookup: off

Hi Guys, Had a samba server up and running on a sparc running 2.6. All was well with the world then I had to move it to another subnet. Since then I have not been able to connect or see it in the browser list and keep seeing the following error in smb.log which I can't find an answer to. The error is ERROR: root did not create the semaphore [1999/12/28 10:04:13, 0]

On Wed, 2003-11-12 at 11:45, Vikram Adve wrote: > > This implies that it is not intended for end-user consumption but more > > for a proof-of-concept and ongoing research potential. > > You're being too modest, Misha --- this is going to be the Linux of the > future :) > I'll add my pragmatist $0.02 worth here. Take it with a grain of salt. If LLVA isn't

On Wed, Nov 12, 2003 at 04:05:20PM -0800, Reid Spencer wrote: > On Wed, 2003-11-12 at 11:45, Vikram Adve wrote: > > > This implies that it is not intended for end-user consumption but > > > more for a proof-of-concept and ongoing research potential. > > > > You're being too modest, Misha --- this is going to be the Linux of > > the future :) > >

He everyone, I have a Tripplite SMART700DVa using the tripplite_usb from NUT 2.5 (rev 2217) driver running in Solaris 10x86. My driver hangs when trying to connect. Once the driver sends the watchdog command ("W\0"), it can no longer receive any signals and eventually exits. The UPS responds to other watchdog commands ("W5" for example), but there doesn't seem to be

Short version - can I run NUT on an AIX box with UPS that has a USB interface, like a Tripplite OMNI1500 XL? I downloaded the source and compiled it, but then noticed that while the source file tripplite_usb.c file is present, it wasn't compiled (this is the driver shown on the compatibility list for my ups). So I started looking at the make files and noticed there were no entries in

I got FreeBSD up and running last night (many thanks to Charles Sprickman for a ton of useful suggestions along the way), and took a look at tripplite_usb on an OMNIVS1000. The tripplite_usb driver basically sends old-school Tripp Lite serial commands to the UPS via HID SetReport packets, and receives responses over the first Interrupt IN pipe. Later UPSes seem to be more deterministic in this

Hi, I'm working with svn trunk rev 815, testing tripplite_usb with this model. I haven't gotten far in my testing, but thought I'd notify the list of this error message. Is this message of any consequence, and is it worthwhile for me to continue testing prior to resolving this? I am happy to help debug any driver issues, so please let me know if I can be of assistance. My platform

On May 25, 2016, at 9:42 PM, Larry Fahnoe <fahnoe at fahnoetech.com> wrote: > > So the current NUT can't cause this UPS to power off the load while it is on line power, correct? I will update the nut-server init script with the sleep/reboot logic per FAQ #51. Correct. > My larger concern is testing the UPS to ensure it shuts down correctly and comes back up correctly as

Is there a particular reason why we are setting the alternate interface to 0 in drivers/libusb.c? I have seen some documentation which indicates that this should already done by the OS when the device is enumerated. If that is the case, then there is no reason why we should hardcode the alternate interface to 0. If I remove the following code, tripplite_usb seems to work*:

Charles, The same remarks as for the reconnect_ups() patch for usbhid-ups.c go for the function with the same name in tripplite_usb.c. This is also blocking and thereby locking up the communication between driver and server. I don't think this is intentional, since the MAX_RECONNECT_TRIES in usb_comm_fail() is effectively a no-op then. I also seems to duplicate some things in usb_comm_fail(),

On May 25, 2016, at 3:43 PM, Larry Fahnoe wrote: > > 0.016075 Initiating UPS shutdown > 0.016117 soft_shutdown(offdelay=64): N > 0.016137 send_cmd(msg_len=4, type='N') The delay command ('N') was sent successfully, so the UPS is receiving commands. > 2.117586 send_cmd(msg_len=2, type='G') > 3.219418

Hi, my nut version is 2.2.2-6.4, debian lenny The ups we use is a tripplite OMNIVS1000 USB The drivers i tried are tripplite_usb and usbhid-ups, googled very long about the problems, but didn't get it to run. Does someone has experiences or similar problems? lsusb and lsmod are all right in /etc/udev/rules.d/52_nut-usbups.rules I found one line according to the modell ---- # Tripp Lite -

On 6/21/07, Arjen de Korte <nut+devel at de-korte.org> wrote: > Charles, > > The same remarks as for the reconnect_ups() patch for usbhid-ups.c go for > the function with the same name in tripplite_usb.c. This is also blocking > and thereby locking up the communication between driver and server. I > don't think this is intentional, since the MAX_RECONNECT_TRIES in >