|
Of course, it's on an NT server, so permissions are defined by the NT administrator. > -------- Original Message -------- > Subject: Re: QNTC and qsyseteuid > From: rob@xxxxxxxxx > Date: Tue, July 12, 2005 2:55 pm > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > And would the moral of that story be, don't use group profiles in the IFS > - use an authorization list instead? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > Ed Fishel <edfishel@xxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 07/12/2005 01:52 PM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > cc > > Subject > Re: QNTC and qsyseteuid > > > > > > > michael wrote on 07/12/2005 11:19:00 AM: > > > I want to copy a file to an NT server. The permissions are set up > > correctly on the server. If I sign on as the 'special' user, I can use > > WRKLNK or CPY and access the file. If I use qsyseteuid I can access the > > directory (and any subdirectories) but not a file. If I SBMJOB and > > specify USER('special user') I can also access the file. > > > > Anyone have insight as to why qsyseteuid would allow me to access the > > directory and not the file in the directory? > > The difference between qsyseteuid and the other two is that when you use > qsyseteuid you are setting the effect user id of your thread to the > 'special' user but you are retaining your current group profiles. You are > also not picking up any group profiles of the 'special' user the way you > would on a sign-on or SBMJOB. So it sounds like the 'special' user has > authority to the directories but their group has authority to the files in > those directories. > > Ed Fishel, > edfishel@xxxxxxxxxx > > -- > 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. > > > -- > 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-2025 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.