Now FB is fixed: daqd and nds are running
When I rebooted FB, I noticed that any of the nfs file systems were not mounted.
I started tracking down the issues from here.
I googled the common issues of the nfs mounting during the boot sequence.
- It is good to give "_netdev" option to fstab to mount the system after the network connection is established.
- "auto" option specifies that the file system is mounted when mount -a is run
Resulting /etc/fstab is this:
/dev/sdb1 / ext3 noatime 0 1
/swapfile none swap sw 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
/dev/sda1 /frames ext3 noatime 0 0
linux1:/home/cds/ /cvs/cds nfs _netdev,auto,rw,bg,soft 0 0
linux1:/home/cds/rtcds /opt/rtcds nfs _netdev,auto,rw,bg,soft 0 0
linux1:/home/cds/rtapps /opt/rtapps nfs _netdev,auto,rw,bg,soft 0 0
linux1:/home/cds/caltech/apps/linux /opt/apps nfs _netdev,auto,rw,bg,soft 0 0 |
But this didn't help mounting the nfs file systems at boot yet. I dug into google again and found a command "/sbin/rc-update".
"/sbin/rc-update show" shows what services are activated at boot. It did not include "nfsmount". So the following command
was executed
> sudo /sbin/rc-update add nfsmount boot
> /sbin/rc-update show
* Broken runlevel entry: /etc/runlevels/boot/portmap
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
consolefont | boot
dcron | default
dhcpd | default
hostname | boot
in.tftpd | boot
keymaps | boot
local | default nonetwork
localmount | boot
modules | boot
monit | default
mx | default
net.eth0 | default
net.lo | boot
netmount | default
nfs | boot
nfsmount | boot
rmnologin | boot
rpc.statd | boot
sshd | boot
syslog-ng | boot
udev-postmount | default
urandom | boot
xinetd | default |
After rebooting, I confirmed that the nfs file systems are correctly mounted
and daqd and nds are automatically started.
This means that FB had never been configured to run correctly at boot. Shame on you! |