LILiK
/
openwrt-packages-dist
5
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
12413 Commits
1 Branch
46 MiB
Tree: 3b5a8eee84
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '3b5a8eee84'
${ noResults }
openwrt-packages-dist/net/nut/files/nut_server

24 lines
568 B
Raw Normal View History

net/nut: Build optional separate packages and ucify With a LuCI app (of which I have one written) ucification makes sense (and is in fact needed), so ucify the initscripts. Also, rather than making selection of things to include an image a matter of selecting compile-time config options, make optional things into seperate packages that are built in default builds, and leave selection of what to include or not up to the user (e.g. using ImageBuilder, or adding packages via opkg). Signed-off-by: Daniel Dickinson <lede@cshore.thecshore.com>
8 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
nut: Reorganize nut-server to clarify nut-driver Clarify the different between the common nut-driver portions of nut-server and the nut-server (upsd) proper. nut-driver can't be used without nut-server so there is no compelling reason to split into a separate package, but the reorganization makes such a move easier and makes it clear what each bit is for. While we continue to use a single initscript, it's a properly procdified one which handles the upsd daemon as a different instance than the driver instances. This resolves a race condition in which upsd and drivers fail to start do to a degree of interdepedence. Also properly 'procd'ifies the nut-server initscript. Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
6 years ago
net/nut: Build optional separate packages and ucify With a LuCI app (of which I have one written) ucification makes sense (and is in fact needed), so ucify the initscripts. Also, rather than making selection of things to include an image a matter of selecting compile-time config options, make optional things into seperate packages that are built in default builds, and leave selection of what to include or not up to the user (e.g. using ImageBuilder, or adding packages via opkg). Signed-off-by: Daniel Dickinson <lede@cshore.thecshore.com>
8 years ago
​
 
  1. #config driver 'upsname'
  2. #	option driver usbhid-ups
  3. #	option port auto
  4. #	option other other-value
  5. #	option runas root
  6. 

  7. #config user
  8. #	option username upsuser
  9. #	option password upspassword
  10. #	option actions optional-action
  11. #	list instcmd optional-instant-command
  12. #	option upsmon slave|master
  13. 

  14. #config listen_address
  15. #	option address ::1
  16. #	option port 3493
  17. 

  18. #config upsd 'upsd'
  19. #	option maxage 15
  20. #	option statepath /var/run/nut
  21. #	option maxconn 1024
  22. #	option runas nut
  23. # NB: certificates only apply to SSL-enabled version
  24. #       option certfile /usr/local/etc/upsd.pem