Moxa TC-6110-T-LX [52/117] Setting up hot swap daemon logging

Moxa TC-6110-T-LX [52/117] Setting up hot swap daemon logging
TC-6110 Linux User's Manual Managing Communications
3-34
devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
none on /tmp type tmpfs (rw,relatime)
/dev/hda2 on /home type ext2 (rw,relatime,errors=continue)
/dev/sda1 on /media/disk2p1 type ext3
(rw,relatime,errors=continue,data=ordered)
/dev/sda2 on /media/disk2p2 type ext3
(rw,relatime,errors=continue,data=ordered)
/dev/sdb1 on /media/disk1p1 type ext3
(rw,relatime,errors=continue,data=ordered)
/dev/sdb2 on /media/disk1p2 type ext3
(rw,relatime,errors=continue,data=ordered)
2. The X1 button on the spine of a drive module is pressed
On the spine of each module there is an inset button labeled X1; this button may be custom-configured, but
by default it signals the OS to un-mount the hard drive so that the module may be safely removed. Users
should use a small screwdriver or other sharply tipped instrument to gently depress the X1 button.
When the X1 button is pressed less than 5 seconds (i.e.: a short press),
the
./etc/mxhtspd/action-btn-pressed script will be executed. It will umount all partitions on that
module, and when it is completed the LEDs on the module spine will blink 3 times, at 1 second intervals, to
indicate that the disk has been successfully unmounted. Users may then remove the module from the slot.
3. A drive is removed without being properly unmounted
The only purpose of this script is to warn of misuse through incorrect operation of the drive modules.
When disk n is unplugged, the
/etc/mxhtspd/action-disk-unplugged script will be triggered with
argument n. It will check if all partitions on the module were umounted before they were unplugged and
warn the user if they weren’t. Users should remember: the correct procedure to remove a module is to first
depress the X1 button on the spine of the module, and wait for the partitions to unmount. Only then should
they remove the module.
4. A monitored partition has reached or is over a specified allocation limit; or it does not exist
When /media/diskNpM has allocated its storage space to the limit defined in
/etc/mxhtspd/mxhtspd.conf, mxhtspd will display an error message and blink the warning LED N at
1 second intervals. In addition, the
/etc/mxhtspd/action-part-over-usage script will be launched
with argument
/media/diskNpM.
WARNING!
B
e sure to press the X1 button on the spine of the storage module before removing it. After depressing the
button (for which you should use a small screwdriver, or other pointed instrument), the LEDs will blink 3 times
to indicate that
the disks have been successfully unmounted. You may then safely remove the
drive modules
from the computer.
Setting Up Hot Swap Daemon Logging
This section describes associate mxhtspd log messages with the rsyslogd daemon.
1. Check the system run level by running the command:
moxa@Moxa:~# sudo runlevel
N 2
2. If the runlevel is 2, then skip this step. If it is not, then either modify inittab (/etc/inittab) so that the
default runlevel is 2, or add a symlink that will call mxhtspd to the runlevel for which the machine is
currently configured. To set the inititialization table (/etc/inittab) to runlevel 2, edit two lines near the top
so that they look like this:

Содержание

Похожие устройства

Скачать