search for: proskuri

# reboot Connection to 192.168.5.81 closed by remote host. Connection to 192.168.5.81 closed. ppo at admin:/tmp$ ssh root at 192.168.5.81 root at 192.168.5.81's password: Last login: Tue Jul 30 14:10:49 2013 from pc-ppo.kh.ektos OpenBSD 5.3 (GENERIC.MP) #58: Tue Mar 12 18:43:53 MDT 2013 # ps -aux | grep ups root 2254 0.0 0.0 324 700 p0 S+ 5:29PM 0:00.00 grep ups # ps -aux

Thanks for you reply. I have installed asciidoc with "pkg_add asciidoc" And it returns something: # asciidoc fgh asciidoc: FAILED: input file /root/nut/fgh missing # which asciidoc /usr/local/bin/asciidoc Maybe there is any way to skip building man pages. This is not the such main thing as a new devices support. I also could built the driver that I need # make riello_ser but I don't

another attempt: # upsd Network UPS Tools upsd 2.6.5 fopen /var/db/nut/upsd.pid: No such file or directory listening on 127.0.0.1 port 3493 listening on ::1 port 3493 Can't connect to UPS [senpro] (riello_ser-senpro): No such file or directory # ls -la /var/db/nut/ total 12 drwx------ 2 _ups wheel 512 Jul 30 10:22 . drwxr-xr-x 10 root wheel 512 Jul 29 16:41 .. -rw-r--r-- 1 _ups

Here is what I did: # cd /root/nut/ # nut here it's checkouted repository # ./configure --with-user=_ups --with-group=_ups # cd drivers/ # make riello_ser # chgrp bin riello_ser # cp riello_ser /usr/local/bin # here I copied builder driver to folder where nut-package will store their files/drivers # pkg_add nut-2.6.5p1 # ls -la /dev/tty00 crw-rw---- 1 _ups _ups 8, 0 Jul 30

I'll test it. I'm a bit confused with cgi-bin. I have made a lot of hosts.conf copies and didn't understand where does upsstats trying to find hosts.conf # ps -aux | grep ups _ups 13934 0.0 0.0 484 920 ?? Ss 5:41PM 0:01.53 /usr/local/bin/riello_ser -a senpro _ups 9171 0.0 0.1 532 1168 ?? Ss 5:41PM 0:00.13 /usr/local/sbin/upsd _ups 16906 0.0 0.1

Hello list, I have explored https://github.com/networkupstools/nut repository and found that Riello UPS added into list of supported UPS. But current package for most distribution it's nut-2.6.5 which doesn't have Riello's models. Do we need to wait next upcoming nut release to get start with Riello? I tried to install from source but stuck: # git clone

You are right. Before install nut-cgi I have stopped apache and started it again without chroot. I have started it again with chroot and cgi is working! This is best support for open source project I have ever seen. Good luck! On Thu, Aug 1, 2013 at 3:03 PM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 31, 2013, at 11:39 AM, Pavel Potcheptsov (EKTOS) wrote: > > >

Thank you very much!! I have tried configure downloaded source with # ./configure --with-user=_ups --with-group=_ups --with-statepath=/var/db/nut/ and then build driver and copy again. but this doesn't help (driver pid still in the /var/state/ups). Maybe I must add more arguments to change driver's pid location, but I did next, I changed this argument in openbsd ports: # pkg_delete nut #

On Jul 30, 2013, at 3:28 AM, Pavel Potcheptsov (EKTOS) wrote: > another attempt: > # upsd > Network UPS Tools upsd 2.6.5 > fopen /var/db/nut/upsd.pid: No such file or directory > listening on 127.0.0.1 port 3493 > listening on ::1 port 3493 > Can't connect to UPS [senpro] (riello_ser-senpro): No such file or directory We need to determine whether upsd and the driver are

On Jul 29, 2013, at 7:56 AM, Charles Lepple wrote: > On Jul 29, 2013, at 6:43 AM, Pavel Potcheptsov (EKTOS) wrote: > >> Hello list, >> I have explored https://github.com/networkupstools/nut repository >> and found that Riello UPS added into list of supported UPS. >> But current package for most distribution it's nut-2.6.5 which >> doesn't have

On Jul 29, 2013, at 6:43 AM, Pavel Potcheptsov (EKTOS) wrote: > Hello list, > I have explored https://github.com/networkupstools/nut repository > and found that Riello UPS added into list of supported UPS. > But current package for most distribution it's nut-2.6.5 which > doesn't have Riello's models. > Do we need to wait next upcoming nut release to get start with

Network UPS Tools version 2.7.1 has been released: http://www.networkupstools.org/ This release is an interim release, part of the testing series, and the first release after the transition from Subversion to Git. The last release (2.6.5) is almost a year old. A lot of work has been done, but a good amount remains to achieve 2.8.0 goals. Direct access: - Download:

Hi, I am unable to get upssched working correctly as my UPS calls low battery too late and there is no way to change it. I am running Nut 2.7.3 on Ubuntu 14.04 I have made this script, called /sbin/upssched-cmd.sh #!/bin/sh case $1 in onbatt) /sbin/upsmon -c fsd;; *) echo "shutdown implemented";; esac I am trying to run the script manually to break down my issues. All that

On Jul 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

On Jul 31, 2013, at 3:36 AM, Pavel Potcheptsov (EKTOS) wrote: > Does it looks good? I think so - 40.8 volts with a nominal of 36 volts is 13.6 V/cell, which agrees with the 100% charge value. Hopefully the line voltages and frequency make sense for your region. > Another question what does riello experimental driver warning mean? We add that to all new drivers. This driver was written by