|
Jack,
Thanks for your suggestion. I issued another mount command with the
updated options. Unfortunately, that did not remedy the problem.
Erick
On Tue, May 10, 2011 at 11:22 AM, Jack Kingsley
<iseriesflorida@xxxxxxxxx> wrote:
maybe try something like this:path.
OPTIONS('rw,nosuid,retry=5,rsize=8096,wsize+
=8096,timeo=20,retrans=5,acregmin=30,acregm+
ax=60,acdirmin=30,acdirmax=60,soft') +
CCSID(*BINARY *ASCII)
On Tue, May 10, 2011 at 1:27 PM, Erick Garske <egarske@xxxxxxxxx> wrote:
I am attempting to mount an external drive from my PC to a directory
on the IFS. Once this is complete, I would like to use the CPY command
to transfer files from
the IFS to the mounted drive. In preparation for this I have loaded
Unix Services for Windows on my Windows XP system. Additionally, I
have ensured that the service 'Service for NFS' is up and running.
Next, from Windows Explorer, I created a share and disabled the read
only attribute. Additionally, on the NFS sharing tab, I allowed for
anonymous access and in the NFS Share Permissions window, I set the
type of access to 'Read-Write' and marked the check box 'Allow root
access'.
MOUNT TYPE(*NFS) MFS('192.168.89.2:/otirv-backups')
MNTOVRDIR('/home/mymount')
File system mounted.
CPY OBJ('/home/egarske/msgq.txt') TODIR('/home/mymount')
Not authorized to object. Object is /home/mymount/msgq.txt.
Cause . . . . . : You do not have the correct authority for object
/home/mymount/msgq.txt or for one of the directories in the object
list
After seeing this message and searching on the CPF code, CPFA09C, I
dismounted the drive
and issued the command below to relax the authority:
chmod a=rwx otirv-backups
But after remounting the drive and attempting to copy, I received the
same error message.
Is there a configuration step that I am missing that would enable the
authority to be relaxed enough to allow a file to be copied to the
share?
Thanks.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.