[U2] PI/Open on UNIX problem
I hope there are some old-timers on the list who will have some thoughts about a PI/Open problem one of my clients is having. In PI/Open you can define a verb to execute O/S level commands. Here's an example: LS 0001: V 0002: ls 0003: PR The PR in field 3 defines the verb as a primitive; i.e. an O/S level command. Problem is that when any user other than root executes the command (or any other primitive) it fails and puts this sort of warning into the PILOG file: # cat WARN.26835 [PI/open Rev. 3.7.6] [Copyright (c) 1992 Prime Computer, Inc.] [Copyright (c) 1994 VMark Software, Inc.] User name : jaftest PI User number : 12 Process ID : 10934 Hostname : dtcc271 ISYS pathname : /u/isys VOC pathname : ./VOC ACCOUNT path : /u/isys WARN.26835 logged at Thu Jan 31 17:01:38 2008 *** Status 13 (OS: Permission denied), severity WARNING Detected by the DISKIO subsystem in fds_os_open at location 3. Called from fds_open at location 4. *** Status 13 (OS: Permission denied), severity WARNING Detected by the DISKIO subsystem in fds_os_open at location 3. Called from fds_open at location 4. The warning implies a permissions problem; but all the components to the user account, including the VOC, have permissions of 777 (read/write/execute) for everyone. At the UNIX level there is no problem executing the command, so this is a PI/Open issue. The problem occurs across the board, in all accounts. I've set 777 permissions on everything in the isys directory as well. Feels like some sort of PI/Open security thing... If anyone has thoughts I'd sure appreciate it! Jeff Fitzgerald Fitzgerald Long, Inc. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] PI/Open on UNIX problem
Check the permissions on /var/tmp. Programs such as trace, tusc, and truss are useful for tracking down such problems. On my system, this is what happens (edited for brevity): open(/var/tmp/aaa_8ai91, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 12 write(12, p w d , 4)= 4 write(12, \n e c h o $ ?/ v.., 28) = 28 close(12) = 0 fork() open(/var/tmp/baaa9ai91, O_RDONLY)= 12 read(12, 0\n, 2048) = 2 close(12) = 0 unlink(/var/tmp/aaa_8ai91)= 0 unlink(/var/tmp/baaa9ai91)= 0 Henry Henry P. Unger Hitech Systems, Inc. [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Fitzgerald Sent: Saturday, February 02, 2008 09:41 To: u2-users@listserver.u2ug.org Subject: [U2] PI/Open on UNIX problem I hope there are some old-timers on the list who will have some thoughts about a PI/Open problem one of my clients is having. In PI/Open you can define a verb to execute O/S level commands. Here's an example: LS 0001: V 0002: ls 0003: PR The PR in field 3 defines the verb as a primitive; i.e. an O/S level command. Problem is that when any user other than root executes the command (or any other primitive) it fails and puts this sort of warning into the PILOG file: # cat WARN.26835 [PI/open Rev. 3.7.6] [Copyright (c) 1992 Prime Computer, Inc.] [Copyright (c) 1994 VMark Software, Inc.] User name : jaftest PI User number : 12 Process ID : 10934 Hostname : dtcc271 ISYS pathname : /u/isys VOC pathname : ./VOC ACCOUNT path : /u/isys WARN.26835 logged at Thu Jan 31 17:01:38 2008 *** Status 13 (OS: Permission denied), severity WARNING Detected by the DISKIO subsystem in fds_os_open at location 3. Called from fds_open at location 4. *** Status 13 (OS: Permission denied), severity WARNING Detected by the DISKIO subsystem in fds_os_open at location 3. Called from fds_open at location 4. The warning implies a permissions problem; but all the components to the user account, including the VOC, have permissions of 777 (read/write/execute) for everyone. At the UNIX level there is no problem executing the command, so this is a PI/Open issue. The problem occurs across the board, in all accounts. I've set 777 permissions on everything in the isys directory as well. Feels like some sort of PI/Open security thing... If anyone has thoughts I'd sure appreciate it! Jeff Fitzgerald Fitzgerald Long, Inc. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] PI/Open on UNIX problem
How about permissions on the command itself. I would imagine that
PI/Open is somehow opening a shell to execute the command and who knows
what user its using ('nobody' perhaps). I'd try changing permissions on
'ls' to 777.
Jeff Fitzgerald wrote:
I hope there are some old-timers on the list who will have some thoughts
about a PI/Open problem one of my clients is having.
In PI/Open you can define a verb to execute O/S level commands. Here's
an example:
[snip]
Jeff Schasny - Denver, Co, USA
IT Wrangler
jschasny at gmail dot com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] PI/Open on UNIX problem
Bingo! Changing permissions on /var/tmp solved the problem! Henry, as always, you were spot on. Thanks a million! Jeff Fitzgerald Fitzgerald Long, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henry Unger Sent: Saturday, February 02, 2008 11:48 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] PI/Open on UNIX problem Check the permissions on /var/tmp. Programs such as trace, tusc, and truss are useful for tracking down such problems. On my system, this is what happens (edited for brevity): open(/var/tmp/aaa_8ai91, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 12 write(12, p w d , 4)= 4 write(12, \n e c h o $ ?/ v.., 28) = 28 close(12) = 0 fork() open(/var/tmp/baaa9ai91, O_RDONLY)= 12 read(12, 0\n, 2048) = 2 close(12) = 0 unlink(/var/tmp/aaa_8ai91)= 0 unlink(/var/tmp/baaa9ai91)= 0 Henry Henry P. Unger Hitech Systems, Inc. [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Fitzgerald Sent: Saturday, February 02, 2008 09:41 To: u2-users@listserver.u2ug.org Subject: [U2] PI/Open on UNIX problem I hope there are some old-timers on the list who will have some thoughts about a PI/Open problem one of my clients is having. In PI/Open you can define a verb to execute O/S level commands. Here's an example: LS 0001: V 0002: ls 0003: PR The PR in field 3 defines the verb as a primitive; i.e. an O/S level command. Problem is that when any user other than root executes the command (or any other primitive) it fails and puts this sort of warning into the PILOG file: # cat WARN.26835 [PI/open Rev. 3.7.6] [Copyright (c) 1992 Prime Computer, Inc.] [Copyright (c) 1994 VMark Software, Inc.] User name : jaftest PI User number : 12 Process ID : 10934 Hostname : dtcc271 ISYS pathname : /u/isys VOC pathname : ./VOC ACCOUNT path : /u/isys WARN.26835 logged at Thu Jan 31 17:01:38 2008 *** Status 13 (OS: Permission denied), severity WARNING Detected by the DISKIO subsystem in fds_os_open at location 3. Called from fds_open at location 4. *** Status 13 (OS: Permission denied), severity WARNING Detected by the DISKIO subsystem in fds_os_open at location 3. Called from fds_open at location 4. The warning implies a permissions problem; but all the components to the user account, including the VOC, have permissions of 777 (read/write/execute) for everyone. At the UNIX level there is no problem executing the command, so this is a PI/Open issue. The problem occurs across the board, in all accounts. I've set 777 permissions on everything in the isys directory as well. Feels like some sort of PI/Open security thing... If anyone has thoughts I'd sure appreciate it! Jeff Fitzgerald Fitzgerald Long, Inc. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
