Difference between revisions of "Lentil"
From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search| Line 109: | Line 109: | ||
== rc.local Configuration == | == rc.local Configuration == | ||
This script is modified to run commands when the system is done powering on. | This script is modified to run commands when the system is done powering on. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | This will send the boot.log to npg-admins everytime the pc is started. | |
| − | + | mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log | |
| − | |||
| − | mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log | ||
| − | |||
== Hardware Information == | == Hardware Information == | ||
Revision as of 13:49, 2 June 2009
General Information
Lentil performs backups. Its backup script needs further investigation to determine exactly how it works.
Network Configuration
Hostnames: lentil.unh.edu, lentil.farm.physics.unh.edu
Currently connected to the unh and farm networks via the switch and VLAN.
ifconfig
eth0 Link encap:Ethernet HWaddr 00:23:54:BC:70:F1
inet addr:10.0.0.250 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::223:54ff:febc:70f1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30404 errors:0 dropped:0 overruns:0 frame:0
TX packets:1778 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3723593 (3.5 MiB) TX bytes:227139 (221.8 KiB)
Interrupt:66 Base address:0x6000
eth0.2 Link encap:Ethernet HWaddr 00:23:54:BC:70:F1
inet addr:132.177.88.254 Bcast:132.177.91.255 Mask:255.255.252.0
inet6 addr: fe80::223:54ff:febc:70f1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:28826 errors:0 dropped:0 overruns:0 frame:0
TX packets:1032 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3068357 (2.9 MiB) TX bytes:114723 (112.0 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:99 errors:0 dropped:0 overruns:0 frame:0
TX packets:99 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9335 (9.1 KiB) TX bytes:9335 (9.1 KiB)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:10754 (10.5 KiB)
Access Configuration
/etc/security/access.conf Any valid user can log into lentil from any machine on the Internet.
Backup Configuration
Location of Backups
/mnt/npg-daily/34/
All backup related scripts are:
/etc/auto.npg-daily /usr/local/bin/rsync_backup.pl /etc/cron.daily/0rsync_backup /usr/sbin/vgcfgbackup /etc/rsync-backup.conf
/etc/rsync-backup.conf
# Backups are 'pull' only. Too bad there isn't a better way to enforce this.
read only = yes
# Oh for the ability to retain CAP_DAC_READ_SEARCH, and no other.
#uid = root
# XXX There seems to be an obscure bug with pam_ldap and rsync whereby
# getpwnam(3) segfaults when (and only when) archiving /etc. Using a numeric
# uid avoids this bug. Only verified on Fedora Core 2.
uid = 0
# There's not much point in putting the superuser in a chroot jail
# use chroot = yes
# This isn't really an effective "lock" per se, since the value is per-module,
# but there really ought never be more than one, and it would at least
# ensure serialized backups.
max connections = 1
[usr_local]
path = /usr/local
comment = unpackaged software
[opt]
path = /opt
comment = unpackaged software
[etc]
path = /etc
comment = conf files
[var]
path = /var
comment = user and system storage
SNMP Configuration
/etc/snmp/snmpd.conf Copied from Pepper.
Smartd Configuration
The configuration file is at /etc/smartd.conf. The smartd.conf does a silent check, which only emails reports if the SMART health status comes back as failed. This smartd.conf will look different from alot of the other computers because it doesn't have a RAID card installed, so each disk is mounted seperately for backups.
SMARTD Smartd setup and configuration
rc.local Configuration
This script is modified to run commands when the system is done powering on.
This will send the boot.log to npg-admins everytime the pc is started.
mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log
Hardware Information
Motherboard: Asus P5QL-CM Specifications: Specifications User Manual: V2.pdf Users Manual Memory: 2 GB DDR2 Wake On Lan Command: sudo ether-wake 00:1e:4f:9b:13:90
Fixes
- Kernel Crash Fix (2/24/2009)
