Opened 13 years ago
Last modified 3 years ago
#33433 new enhancement
nut - 2.6.1 - new port for 'nut-client'
Reported by: | gforeman02@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.4 |
Keywords: | nut nut-client | Cc: | miwi@…, cooljeanius (Eric Gallager) |
Port: | nut |
Description
I would like to request a new port for 'nut-client' only install. It should only include functionality needed to monitor a ups on another system.
Attachments (1)
Change History (4)
Changed 13 years ago by gforeman02@…
Attachment: | org.networkupstools.upsmon.plist added |
---|
comment:1 Changed 13 years ago by gforeman02@…
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | miwi@… added |
---|
If you're saying that this is functionality already available, along with other components, in the nut port, and you would like a nut-client port that only includes this capability, and not the other components, then this would be an ideal time to use subports, rather than a complete new port.
comment:3 Changed 3 years ago by cooljeanius (Eric Gallager)
Cc: | cooljeanius added |
---|
Note: See
TracTickets for help on using
tickets.
I was able to get this working via the existing 'nut' macport by doing the following:
port install nut
cp /opt/local/etc/upsmon.conf.sample /opt/local/etc/upsmon.conf
ps -ef | grep upsmon
If you see something like:
You should be good since nut is running two processes. One is for root and the other is for the nut user installed via macports.