For some open source package like Apache, when you *make* it it will create a directory structure like cd ~/mycode/apache *make* ./sbin/ ./etc/ ./var/www/ and when you *make install* it copies those over to the correct system locations /usr/sbin /etc/
For something commercial like Oracle, or not part of the package system it does unto itself likewise ./bin/ ./etc/ ./var/ and *make install* copies it into /opt/oracle/ or /usr/local But they will both run as daemons and their CWD will be /, right? So how does it know that its ./etc is in /etc or if it's in ./opt/oracle/etc or that it's ./lib is /usr/local/lib? Is it just by --prefex and #define throughout the code? I've got a toolkit that appears to expect a particular file to be located in a particular directory in the working directory of the daemon. I don't want to put that directory in /. The simplest solution seems to be to have the daemon script cd /opt/app_name/usr/, but I suspect there is a better solution that I don't yet understand. AJ ONeal
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
