search for: run_as_user

Hi. I have an improvement suggestion. Say that a careless user starts editing upsmon.conf before having read the complete documentation (not that I know of any such users of course) and starts by adding "RUN_AS_USER = nutmon" and then creates this user. Later he discovers that the rpm package already has created a "nut" user and therefore deletes the nutmon user but forgets to update upsmon.conf. In this case usbmon will fail silently to start up, without any clues why. Please add some code to...

...missions. I# For best results, you should create a new normal user like "nutmon", # and make it a member of a "nut" group or similar. Then specify it # here and grant read access to the upsmon.conf for that group. # # This user should not have write access to upsmon.conf. # # RUN_AS_USER nutmon RUN_AS_USER root For security reasons you should change root to another user? which other rights are needed for this user to make it work? Kind Regards, Rob > On 15 Jun 2017, at 21:48, Robbie van der Walle <rvanderwalle at gmail.com> wrote: > > Ok did it again from...

Hello, I would like to know if there is a mean to prevent the driver to drop root privileges through config files ? I have seen the possibility of passing -u root to the driver command line. But I don't see how to use it with my rc-scripts without messing things badly. I have also seen the RUN_AS_USER variable but it seems to apply only to the upsmon client.

After some testing, I notice that my NOTIFYCMD script seems to work if I call it as user 'john' (that's me) but if I call it as 'root' it does not work. So is there a permissions issue ? I have permission on the file set to 755. I see there is a variable in upsmon.conf called RUN_AS_USER. I do not have this defined. Does this variable need to be defined ? I presume that if it is not defined then upsmon is running as root. I saw something about 'user' and 'group' in the documentation but am a bit lost as to what I should do. If this is the problem then explicit in...

The upsmon.conf has the option of setting RUN_AS_USER username Might it be possible to add a similar option to the upsd.conf file? I see the -u command-line option for both upsmon and upsd, however, upsd doesn't seem to carry that to the configuration file, as upsmon does. Thanks.

...3523 Sep 25 20:09 .bashrc -rwxrwx--- 1 nutmon nutmon 220 Apr 18 2019 .bash_logout -rwxrwx--- 1 nutmon nutmon 807 Apr 18 2019 .profile root at nutpi:/etc/nut# grep ^[^#] upsd.users [nutmon] password = <userpwd> upsmon master root at nutpi:/etc/nut# grep ^[^#] upsmon.conf RUN_AS_USER nutmon MONITOR deltec-PRA1500 at localhost 1 nutmon <userpwd> master On Mon, Jan 27, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or...

...1500 on 12334567890" upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL privatenet 192.168.1.0/24 ACCEPT localhost ACCEPT privatenet REJECT all LISTEN 127.0.0.1 3493 upsd.users: [monuser] password = sfdiw3vc allowfrom = localhost upsmon master upsmon.conf: RUN_AS_USER monuser MONITOR apcups at localhost 1 monuser sfdiw3vc master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/logger POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /var/run/killpower RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 Here is the start...

On Thu, 6 Aug 2020, Todd Benivegna wrote: > ... I grep’d the syslog and here’s the results: Could you also grep for upsd and upsmon in the NAS log? Is this possible? > proton at proton:~$ sudo grep upsmon /var/log/syslog > Aug  6 19:19:09 proton upsmon[1552]: UPS ups at 192.168.1.70 on battery > Aug  6 19:19:14 proton upsmon[1552]: UPS ups at 192.168.1.70 on line

...mon nutmon 220 Apr 18 2019 .bash_logout > -rwxrwx--- 1 nutmon nutmon 807 Apr 18 2019 .profile > > root at nutpi:/etc/nut# grep ^[^#] upsd.users > [nutmon] > password = <userpwd> > upsmon master > > root at nutpi:/etc/nut# grep ^[^#] upsmon.conf > RUN_AS_USER nutmon > MONITOR deltec-PRA1500 at localhost 1 nutmon <userpwd> master > > On Mon, Jan 27, 2020 at 7:00 AM < > nut-upsuser-request at alioth-lists.debian.net> > wrote: > > > Send Nut-upsuser mailing list submissions to > > nut-upsuser at alioth-list...

On Jun 18, 2014, at 1:51 PM, Mike. <the.lists at mgm51.com> wrote: > The upsmon.conf has the option of setting RUN_AS_USER username > > Might it be possible to add a similar option to the upsd.conf file? > > I see the -u command-line option for both upsmon and upsd, however, > upsd doesn't seem to carry that to the configuration file, as upsmon > does. I'll admit this does seem arbitrary,...

On 6/19/2014 at 9:03 AM Charles Lepple wrote: |On Jun 18, 2014, at 1:51 PM, Mike. <the.lists at mgm51.com> wrote: | |> The upsmon.conf has the option of setting RUN_AS_USER username |> |> Might it be possible to add a similar option to the upsd.conf file? |> |> I see the -u command-line option for both upsmon and upsd, however, |> upsd doesn't seem to carry that to the configuration file, as upsmon |> does. | |I'll admit this does seem arb...

I just committed the --with-group option for configure. One thing is not quite what I like, but I have no idea how to script this in autoconf. Currently both RUN_AS_USER and RUN_AS_GROUP have the defaults "nobody" and "nogroup" respectively. I think this really should be changed to the following: - if neither --with-user, nor --with-group are specified, we apply the defaults "nobody" and "nogroup" (or whatever are sane defau...

...guration (maybe even simply a permissions problem) since I upgrade today to 2.0.2 I have apcsmart set up and talk to my ups no problem (upsc get answer). I have upsd running no problem! But when I try to start upsmon, it's unable to talk to my upsd. Having try a few option I found that saying RUN_AS_USER=root makes my upsmon runs without any problem. Here is the message I receive from the Debug: rounoff:/var/run/nut# upsmon -D Network UPS Tools upsmon 2.0.2 UPS: bup@localhost (master) (power value 1) Using power down flag file /etc/killpower Trying to connect to UPS [bup@localhost] UPS [bup@loca...

..."getUPSstatus ups at 192.168.1.70 ; logger -t upsmon.conf \"UPS status is $UPSstatus\" ; /sbin/shutdown -h +0" > > Would that not work?  I believe that's what you told me to put there. > > I think I've definitely made a mistake though, in that I have not set RUN_AS_USER in upsmon.conf and set up the appropriate permissions.  I read somewhere that it would then run as user NOBODY and not be able read upsmon.conf.  Is that true?  Could that be the whole problem? > > I'm thinking I need to put in.. > > RUN_AS_USER nut > > in upsmon.conf and then...

...: MODE=standalone /etc/nut/ups.conf : [dell] driver = usbhid-ups port = auto /etc/nut/upsd.conf : LISTEN 127.0.0.1 3493 /etc/nut/upsd.users : [admin] password = **** actions = SET instcmds = ALL [upsmon] password = **** upsmon master /etc/nut/upsmon.conf : RUN_AS_USER nut MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 FINALDELAY 5 MONITOR dell at localhost 1 upsmon **** master /etc/nut/upssched.conf : CMDSCRIPT /etc/nut/sched/upssched.sh (this script exi...

.... It probably better to declare something like SHUTDOWNCMD "logger -t upsmon.conf \"UPS status [$( upsc ups at 192.168.1.70 ups.status )]:$( upsc ups at 192.168.1.70 )\" ; /sbin/shutdown -h +0"   > I think I've definitely made a mistake though, in that I have not set RUN_AS_USER in upsmon.conf The default user is usually set when NUT is built for a specific Linux distribution. I don't know what user Ubuntu have chosen, but I will guess that they have followed Debian and use "nut". I suggest you do not change this. > and set up the appropriate permiss...

...etwork UPS Tools: example upsd configuration file ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all # Network UPS Tools: Example upsd.users [monmaster] password = * allowfrom = localhost actions = SET instcmds = ALL # Network UPS Tools: example upsmon configuration RUN_AS_USER nutmon MONITOR lupin1500AVR@localhost 1 monmaster * master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/local/ups/bin/notifyme POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WAL...

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONB...

...the directory as nutmon nut but changed it to nutmon nutmon to see if that worked. It didn't make a difference. Sorry about the digest this. I needed to hit a line in gmail web client to see the subject line. Know I know. Thanks for the heads up.. [root at donner nut]# grep ^[^#] upsmon.conf RUN_AS_USER nutmon MONITOR deltec-PRA1500 at localhost 1 nutmon zaq12wsx master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /sbin/upssched POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower On Mon, Jan 27, 2020 at 8:32 AM Greg Treantos <gtreanto at gmai...

...this: SHUTDOWNCMD "getUPSstatus ups at 192.168.1.70 ; logger -t upsmon.conf \"UPS status is $UPSstatus\" ; /sbin/shutdown -h +0" Would that not work? I believe that's what you told me to put there. I think I've definitely made a mistake though, in that I have not set RUN_AS_USER in upsmon.conf and set up the appropriate permissions. I read somewhere that it would then run as user NOBODY and not be able read upsmon.conf. Is that true? Could that be the whole problem? I'm thinking I need to put in.. RUN_AS_USER nut in upsmon.conf and then do: $ sudo chown -R root:...