General

ssh CTRL + s recovery

PDF

If you use CTRL + s (software flow control or XOFF/XON flow control) during a ssh session your terminal seems to stop responding to any keystroke.
However, the terminal is still connected, by typing CTRL + s you sent XOFF, meaning transmit off, which pauzes the transmission. CTRL + q, XON, resumes the transmission.
Keep in mind that everything you type after CTRL + s is buffered and will be sent when you resume the transmission with CTRL + q.

Tags:
 

Iomega IX2 (and other NAS devices) making read-only partitions writable

PDF
One of the disadvantages of the Iomega IX2-200 NAS device is that once you want to startup a daemon on startup of want to modify settings which you cant modify by the webinterface, you need to gain access the the shell, edit the neccessary config files or startup scripts, but you face the fact that the partitions are read-only or even if the config file is stored on a writable partition, the modification is not persistant while it will be over written at the next reboot. To solve this you need to make the read-only partition writable.
Tags:
 

Difference between mtime, ctime and atime

PDF
A common mistake is that ctime is the file creation time. This is not correct, it is the inode/file change time. mtime is the file modification time. A often heard question is "What is the ctime, mtime and atime?".This is confusing so let me explain the difference between ctime, mtime and atime.
Tags:
 

How to find out what process is keeping the filesystem busy

PDF
If you ever run in the situation where you try to unmount a file-system but the umount command tells you the 'device is busy' the fuser command might be helpful. fuser provides information about the process keeping the file-system busy by returning you the process-id's. Piping the process-id's to the ps command you can determine more information about each process.
 

System hangs "system message bus"

PDF

Once you have installed and switched to LDAP authentication the system may seem to hang on boot-up when the messagebus daemon tries to initialize. Though eventually after a very long time-out it will continue the boot process. This is related to authentication being required while messagebus daemon starts prior to the LDAP daemon. A quick work-around to solve this issue is to change the boot sequence, the messagebus daemon has to be started after the LDAP daemon. To accomplish this type:

mv /etc/rc.d/rc3.d/S22messagebus /etc/rc.d/rc3.d/S28messagebus
mv /etc/rc.d/rc5.d/S22messagebus /etc/rc.d/rc5.d/S28messagebus
chkconfig --level 4 messagebus off
Tags:
 
  • «
  •  Start 
  •  Prev 
  •  1 
  •  2 
  •  Next 
  •  End 
  • »
Page 1 of 2

Search






You are here: Home Howtos and FAQs General