Terry Spafford writes: > > I just tried to use a local directory instead of absolute directories > and that does seem to work. It's a bit of a cludge but once I tweek the > scripts a bit it will work. Does anyone have any other ideas for making > this work with an absolute path name?
Making -d work correctly in client/server mode is much harder than it appears at first glance. There are some comments in the code about what the problems are and some possible approaches to solving them, but they've been there for quite a long time. Changing directory to the parent directory and using a simple directory name in -d is the only solution at present. > As for why we want to specify directories where code goes, it is because > we have many more customers then we have Alpha's to work on, so Unix > boxes will often be set up to be more then one customer at a time > depending on which binaries are running. So why don't you let the developer choose where the code goes instead of doing it in your script? -Larry Jones When you're SERIOUS about having fun, it's not much fun at all! -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
