-------------------------------------------------------------------------------
Q: Why cannot ramlog start and stop anytime? / What should I do if ramlog says 
   /var/log is in use?

A: Ramlog creates /var/log on ramdisk and all program/daemons using it, need
   to be started after /var/log on ramdisk is created. If you install ramlog,
   deamons are already logging to /var/log, so it is not easy to move it to
   ramdisk. To activate ramlog you should restart the system. Also please check 
   below Q&A.

-------------------------------------------------------------------------------
Q: Do I really have to restart my system because of ramlog?

A: No, you don't. If you do not want to restart the sytem you should stop all 
   the programs/daemons using /var/log. Then you are able to start and stop 
   ramlog anytime. However if you did not update kernel parameter "ramdisk_size"
   or you want to change the size of ramdisk, you have to reboot your system.

-------------------------------------------------------------------------------
Q: Why I cannot see the process of ramlog despite it says it is running?

A: Ramlog is "fake" daemon, it just runs as system service but it does not have
   any process running in the background.

-------------------------------------------------------------------------------
Q: I deleted file in /var/log while ramlog is running but after I rebooted my
   system, the file was back - is it a bug?

A: Not really - ramlog is consistent with logrotate and if you need to delete
   any file in ramlog which is already backed up on hdd, you need to delete
   it in /var/log and /var/log.hdd as well.
   (If this would be real issue for some reason, ramlog can be changed to use
    rsync instead of cp.)
