Displaying 3 results from an estimated 3 matches for "check_var_directory".
2009 May 27
3
This guy must be an idiot
OK, can someone tell me what utterly moronic thing I am doing wrong?
I have two roughly identical Linux system running NUT, and one works
properly. The other almost does. The second system works well once
everything is up, but after booting, the system does not have connectivity
to the UPS. I have to manually run `upsdrvctl start backup`,
`/etc/init.d/nut start`, and `upsd` to get NUT
2007 Feb 06
9
Shutdown problem with Geek Squad GS1285U
...$DEFAULT
pid_dir=/var/run/nut
upsmon_pid=${pid_dir}/upsmon.pid
upsd_pid=${pid_dir}/upsd.pid
upsd=/usr/local/ups/sbin/upsd
upsmon=/usr/local/ups/sbin/upsmon
upsdrvctl=/usr/local/ups/bin/upsdrvctl
log=">/dev/null 2>/dev/null"
# Check if /var/run/nut exists and has the correct perms
check_var_directory() {
[ ! -d ${pid_dir} ] && mkdir -p ${pid_dir} \
&& chown root:nut ${pid_dir} \
&& chmod 770 ${pid_dir}
}
start_stop_server () {
case "$START_UPSD" in
y|Y|yes|YES|Yes)
case "$1" in
start)...
2017 Jun 11
3
Help with Elite 800VA usb UPS
So....seems so better...
Each time I rebbot, I miss the /var/run/nut folder...
root at artu:~# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
Can't chdir to /var/run/nut: No such file or directory
Driver failed to start (exit status=1)
root at artu:~# upsd
Network UPS Tools upsd 2.7.2
fopen