Fileshare server is stopped immediately if started in background; this article explains what to do when this occurs.
Problem:
The fileshare configuration file fs.cfg contains the background switch -b. fs is submitted to the background with:
fs > logfile 2>&1 &
(The last "&" tells UNIX to put the program in the background.)
However, fs reports "stopped" the next time a foreground command is entered or the Enter key is pressed.
Resolution:
Fileshare attempts to write a status message to the terminal screen as it interprets each line found in fs.cfg. The -b background swtich in the configuration file is seen only after the first console output is attempted. It is this attempt that causes fileshare to stop. The workaround is to start fileshare with:
fs -b > logfile 2>&1 &
Fileshare then sees the -b on the command line immediately and outputs nothing to the screen. (The -b switch in fs.cfg is still necessary, however.)