Eric, Ari, and Chuck, Thanks for the continued assistance. It is obviously permissions - and I'm going to tackle this one even if it kills me. Learning OSX's Unix underpinnings, commands, and nature is a bid daunting when added to keeping pace with all the other stuff you have to know to make a living in this field.
Thanks for your help, and guiding this newbie-unix person! -Bill on 2/27/06 08:33, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote: > Guess I should have told you what needs to change once you find the > owner and group of the log files. Use the chown command to change the > owner and group of the folder that the logs will be used in to the > owner and group of the log files. This will allow the WO processes to > write into that logs folder. > > - Eric > > On Feb 25, 2006, at 12:46 PM, WebObjects wrote: > >> It looks as though permissions is the problem. I changed the output >> directory to "/Users/Shared/" and log-output works fine. >> >> Below is a snippet from the head of the log. Someone mentioned >> that you can >> tell from this output what 'user' the application is running >> under. My goal >> is to set the output path to be "/Users/admin/WOLogs/". >> >> Which line of this output divulges the users identity? (the user whose >> identity I'd have to allow permission to 'WOLogs') >> >> Thanks as always, >> >> -Bill >> _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
