> > > 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. > > Are you talking about a gcc cross-compilation toolchain? If so, you > can't move those around. They usually have to be used exactly where they > were built. >
I'm not exactly sure what it is, but it appears to be part of the vendor-specific toolchain and / or toolkit. I've grepped through all of the source we have and can't find any reference to the file - only that the end-result binary matches and there's an error when the file isn't found in the current working directory. The people I'm working with only know that the file needs to be in location x but not why it needs to be there or how it was ever set to be there. But all of that aside, I'm still curious as to how oracle and nginx know where their configuration files are after make && make install. 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
