| Follow @AlanFormy_Duval
United States
Alan has 20 years of IT experience, mostly in the Government and Financial sectors. He started as a Value Added Reseller before moving into Systems Engineering. Alan's background is in high-availability clustered apps. He wrote the 'Users and Groups' and 'Apache and the Web Stack' chapters in the Oracle Press/McGraw Hill 'Oracle Solaris 11 System Administration' book. He earned his Master of Science in Information Systems from George Mason University. Alan is a long-time proponent of Open Source Software.
Authored Comments
You raise a valid concern. It is true that nohup will write to a file called nohup.out. Particularly in production environments, we will want control over this output. Especially, if running more than one process. As an example, if we want to write stderr and stdout to process specific logs, we can do it like this:
nohup myprogram.sh > myprogram.out 2> myprogram.err < /dev/null &
Or, if we want to write both to the same file:
nohup myprogram.sh >myprogram.log 2>&1 < /dev/null &
Thanks for pointing that out.
Absolutely! Being able to build software can teach every user to understand more deeply how it works. Quite often, a package is built in a generic fashion in order to service the wider user base. Subsequently, these builds might lack certain options or optimizations. A sysadmin or engineer should know how to build in order to optimize to their specific needs.