"Larry Hall (Cygwin)" wrote:
> And the fact that he can access it at all through cron suggests that
> something else is going on.
Not at all, that just means that the share has read (but not write)
permissions by the unauthenticated guest user.
Brian
--
Unsubscribe info: http://cygwin.com/
Brian Dessent wrote:
"Larry Hall (Cygwin)" wrote:
the info already provided. But given that the OP was able to list the
contents of the share from cron, he's managed this in some way. Assuming
this information is not faulty, 'smbntsec' may indeed be what he needs to
manipulate permissions on
"Larry Hall (Cygwin)" wrote:
> the info already provided. But given that the OP was able to list the
> contents of the share from cron, he's managed this in some way. Assuming
> this information is not faulty, 'smbntsec' may indeed be what he needs to
> manipulate permissions on these files. Bu
Brian Dessent wrote:
Jerome Fong wrote:
This doesn't seem to help. I re-ran cron_diagnose.sh and made sure I
had ntsec and smbntsec define, but that doesn't seem to help. Am I
suppose to add it to my .profile?
I think Larry might have been a little quick on the trigger to suggest
smbntsec,
Jerome Fong wrote:
Larry Hall (Cygwin) wrote:
Jerome Fong wrote:
Any idea what I need to change since chmod doesn't seem to have any
effect.
Add 'smbntsec' to your global CYGWIN environment variable or to your
service settings (in the registry) for crond and restart crond.
This doesn't se
Jerome Fong wrote:
> This doesn't seem to help. I re-ran cron_diagnose.sh and made sure I
> had ntsec and smbntsec define, but that doesn't seem to help. Am I
> suppose to add it to my .profile?
I think Larry might have been a little quick on the trigger to suggest
smbntsec, as I don't see how
Larry Hall (Cygwin) wrote:
Jerome Fong wrote:
Any idea what I need to change since chmod doesn't seem to have any
effect.
Add 'smbntsec' to your global CYGWIN environment variable or to your
service settings (in the registry) for crond and restart crond.
This doesn't seem to help. I re-ra
Jerome Fong wrote:
Any idea what I need to change since chmod doesn't seem to have any effect.
Add 'smbntsec' to your global CYGWIN environment variable or to your
service settings (in the registry) for crond and restart crond.
--
Larry Hall http://www.rfk.com
R
Interesting problem. I have a nightly build script that has a crontab
entry setup to run at 1:30 a.m. every morning. Besides building, it
also copies my jar files out to a remote, shared file system for
everyone to pickup and deploy in the morning. However, the cron job is
having problems wri
9 matches
Mail list logo
