----- Original Message -----
From: "Larry Hall (Cygwin)"
To: cygwin
Sent: Monday, June 21, 2010 22:06
| On 6/21/2010 2:08 PM, Oren Cheyette wrote:
| > ** apologies about the bad formatting in the earlier reply **
| >
| > Well, I apologize for being dense, but I'm not getting it. I read the
| > document you link to quite a few times before posting my query.
|
| OK, I didn't know that.
|
| > I initially tried running the service under my own account (as
| > suggested in the faq) with my username& password entered at prompts
| > from cron-config. No luck. Then I added the mount point to the system
| > fstab and tried again. No luck. Then I changed cron to run as system
| > rather than user, just to see. Still no luck. I also tried adding my
| > username& password to the registry using passwd -R.
|
| How about skipping the drive altogether and directly mounting the UNC
| path? If that's not working for you, perhaps you want to try just
| doing the simple "net use" syntax to try to flush out the specifics of
| your problem. Again, I'd recommend using UNC paths rather than dealing
| with possible conflicts of network drives (using the same drive
| designation as two different users or in two different contexts can result
| in access problems for the second "use").
|
I agree with Larry. The mount in fstab is S:\SFCore /sfcore
but S: may not me mapped when running as a service.
Use a UNC path in fstab and run the cron daemon as yourself.
Pierre
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
