Difference between revisions of "AVR watch-dog daemon for Linkstation"

From NAS-Central Buffalo - The Linkstation Wiki
Jump to: navigation, search
(avr_evtd AVR daemon)
 
Line 7: Line 7:
  
 
avr_evtd searches for a configuration file located within the /etc/melco at start-up time. If this file does not exist, then it reverts to reading the file located at /etc/default/avr_evtd. Additionally, it periodically checks the root /dev/hda1 partition and the user data partition /dev/hda3 to ensure they are mounted.  Also, if requested, it will determine if sufficient space remains and if not then the AVR is requested to illuminate the DISK LED.  This periodic checking also takes place on the configuration files.  If they are deemed to have been updated, then the daemon will respond accordingly.
 
avr_evtd searches for a configuration file located within the /etc/melco at start-up time. If this file does not exist, then it reverts to reading the file located at /etc/default/avr_evtd. Additionally, it periodically checks the root /dev/hda1 partition and the user data partition /dev/hda3 to ensure they are mounted.  Also, if requested, it will determine if sufficient space remains and if not then the AVR is requested to illuminate the DISK LED.  This periodic checking also takes place on the configuration files.  If they are deemed to have been updated, then the daemon will respond accordingly.
 +
 +
Any failures are normally routed through the log files.  With timed shutdown/power up, a warning will
 +
be broadcast to all users (console message) when within 5 or less minutes of power off.  Also, fan
 +
failure alerts will be broadcast in this fashion.  Failure to determine mounted partition /dev/hda3
 +
will result in the DIAG LED flashing three times, repeatedly.
 +
 +
A new feature of this daemon is the ability to code events for single or groups of days.  This allows
 +
the user to add any number of power-on/off events as required.  This also has the added benifit of
 +
being able to shut down the device for longer periods.  The internal AVR timer has a 12-bit resolution
 +
timer which can power up the linkstation from a maximum of a sixty eight hour sleep: from time of
 +
invocation.  The AVR is updated again at time of power down/shutdown to re-validate the timer, in case
 +
of time updates (either by user or ntp).  This will also preserve the 68 hour sleep resolution.
 +
 +
== Setup ==
 +
 +
/etc/default/avr_evtd configuration file is the fallback file in the event that the stock melco files do not exist.  The file
 +
is read at initial start-up in order to determine if timed shutdown is required and if the disk usage is to
 +
be monitored.  The file should be always located within the /etc/default directory and a sample file is
 +
provided.  The file format is similar to other Unix configuration files -  comments begin with a # character
 +
and extend to the end of the line; blank lines are ignored.  Configuration commands consist of an initial
 +
keyword followed by an argument.  Arguments may be strings or times written in HH:MM (UTC) format.  Optional
 +
arguments are delimited by [ ] in the following descriptions, while alternatives are separated by |.

Revision as of 12:11, 13 July 2006

WORK IN PROGRESS

Description

avr_evtd is an operating system daemon and should be started from /etc/init.d or /usr/local/sbin. It will return immediately, so you don't need to start it with '&'.

avr_evtd is a simple and small user space interface to the Linkstation AVR micro-controller. It doesn't have a lot of special features, but it's main task is to provide 'keep-alive' messages to the Linkstation's on-board AVR device. This device controls/monitors the fan, various LEDs, timed power up and two buttons. This daemon provides the necessary initialisation to the device and also stimulates the LEDs depending on various fault conditions. It also monitors a power button (located at the front) and a reset button (located at the rear).

avr_evtd searches for a configuration file located within the /etc/melco at start-up time. If this file does not exist, then it reverts to reading the file located at /etc/default/avr_evtd. Additionally, it periodically checks the root /dev/hda1 partition and the user data partition /dev/hda3 to ensure they are mounted. Also, if requested, it will determine if sufficient space remains and if not then the AVR is requested to illuminate the DISK LED. This periodic checking also takes place on the configuration files. If they are deemed to have been updated, then the daemon will respond accordingly.

Any failures are normally routed through the log files. With timed shutdown/power up, a warning will be broadcast to all users (console message) when within 5 or less minutes of power off. Also, fan failure alerts will be broadcast in this fashion. Failure to determine mounted partition /dev/hda3 will result in the DIAG LED flashing three times, repeatedly.

A new feature of this daemon is the ability to code events for single or groups of days. This allows the user to add any number of power-on/off events as required. This also has the added benifit of being able to shut down the device for longer periods. The internal AVR timer has a 12-bit resolution timer which can power up the linkstation from a maximum of a sixty eight hour sleep: from time of invocation. The AVR is updated again at time of power down/shutdown to re-validate the timer, in case of time updates (either by user or ntp). This will also preserve the 68 hour sleep resolution.

Setup

/etc/default/avr_evtd configuration file is the fallback file in the event that the stock melco files do not exist. The file is read at initial start-up in order to determine if timed shutdown is required and if the disk usage is to be monitored. The file should be always located within the /etc/default directory and a sample file is provided. The file format is similar to other Unix configuration files - comments begin with a # character and extend to the end of the line; blank lines are ignored. Configuration commands consist of an initial keyword followed by an argument. Arguments may be strings or times written in HH:MM (UTC) format. Optional arguments are delimited by [ ] in the following descriptions, while alternatives are separated by |.