Hi, I'm running PRO-IV 6.1 in Red Hat Linux. Have a directory with read only permission (-rwxrwxr-x). In the directory I have a PROISAM file and a Cisam file with the same permission (-rwxrwxr-x). From PRO-IV I'm able to read the records from the proisam file, but when trying to read the records from the Cisam file I'm getting ERROR IN OPENING FILE.
If I change the file permission to (-rwxrwxrwx) I'm able to read the records from the Cisam file.
Do you know why this could be happening?, or how can it be solved?
Click the link below to see the new game I'm developing!
3 replies to this topic
#2
Glenn Meyers
-
- Members
-
- 221 posts
ProIV Guru
- Gender:Male
- Location:St. Louis, MO, United States
- Interests:I also raise African Gray Parrots and build hot rod automobiles.
Posted 10 March 2009 - 05:10 PM
Sounds like file ownership issue to me.
Try doing a CHOWN on the file.
Make sure the owners are all in the same group nd have access permissions.
Try doing a CHOWN on the file.
Make sure the owners are all in the same group nd have access permissions.
#3
fuentevilla
-
- Members
-
- 7 posts
Newbie
- Gender:Male
- Location:Mexico
Posted 10 March 2009 - 07:15 PM
Actually the owner and group are not the same for user thats trying to view the content of the files, but that's the requirement, the problem here is that with the same file permission I'm able to view the content of the proisam file and it's not doing the same for the Cisam file. Here is the ls -l :
-rwxrwxr-x 1 root root 1024 Mar 9 17:02 PRUEBA_CISAM.dat
-rwxrwxr-x 1 root root 3072 Mar 9 17:02 PRUEBA_CISAM.idx
-rwxrwxr-x 1 root root 1024 Mar 9 17:04 prueba_pro.pro
User running proiv is pro61 and the group is pro61.
-rwxrwxr-x 1 root root 1024 Mar 9 17:02 PRUEBA_CISAM.dat
-rwxrwxr-x 1 root root 3072 Mar 9 17:02 PRUEBA_CISAM.idx
-rwxrwxr-x 1 root root 1024 Mar 9 17:04 prueba_pro.pro
User running proiv is pro61 and the group is pro61.
Sounds like file ownership issue to me.
Try doing a CHOWN on the file.
Make sure the owners are all in the same group nd have access permissions.
#4
Richard Bassett
-
- Members
-
- 707 posts
ProIV Guru
- Gender:Not Telling
- Location:Rural France
Posted 12 March 2009 - 11:41 AM
CAVEAT: Educated guesswork follows
What's probably happening here is simply that the requirements of the Pro-ISAM and C-ISAM drivers in PROIV are different. Historically, PROIV always required read-write access to application files. Pro-ISAM is a special case because it is the filesystem supplied with PROIV and used for the bootstrap. At some point changes were made to support a read-only bootstrap so, for example, it's possible that the Pro-ISAM driver tries to open a file in read-write mode but is happy to retry in read-only mode if that fails. This may well not be true of the C-ISAM driver, and if so it would probably not be considered a "bug".
HTH
What's probably happening here is simply that the requirements of the Pro-ISAM and C-ISAM drivers in PROIV are different. Historically, PROIV always required read-write access to application files. Pro-ISAM is a special case because it is the filesystem supplied with PROIV and used for the bootstrap. At some point changes were made to support a read-only bootstrap so, for example, it's possible that the Pro-ISAM driver tries to open a file in read-write mode but is happy to retry in read-only mode if that fails. This may well not be true of the C-ISAM driver, and if so it would probably not be considered a "bug".
HTH
Nothing's as simple as you think
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
