System command on FreeBSD...

[Scott Walker]

-----Original Message-----
From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of Chad
McWilliams
Sent: Wednesday, December 29, 2004 1:17 PM
To: 'filePro List'
Subject: RE: System command on FreeBSD...


> > I am in the process of migrating from SCO to FreeBSD. I
> have installed
> > the FreeBSD version of filePro, and have run into the following
> > problem:
> >
> > On SCO when user bob runs the system command to run another FP
> > program, @id shows bob in the new program.
> 
> > On FreeBSD when user bob does the same thing, @id shows
> filepro in the
> > new program.
> 
> > Is there away around this so that I get the SCO behavior of
> the system
> > command?
> 
> Not as far os the OS is concerned, and I don't know how FP
> handles things internally in this regard. The BSD systems 
> handle this differently than the Unix systems systems do. I 
> think this goes back to the days when BSD was forked from 
> Version 7 [ or a release thereafter].
> 
> > I have played with PFSYSEUID to no avail.
> 
> > I'm running FreeBSD 4.9, filePro 5.0.13R4.
> 
> What is it you are trying to accomplish?
> --

We have a function set up that allows a user to switch to another menu
(say from order entry to customer master) to look up something.  The
problem is that under BSD when they do that, the other program is run as
the user (@id) of filepro, rather then their user id.  We have a
security routine that checks whether they are allowed to do what they
are attempting it, and it uses @id lookup the user by.

Does this make sense?

-Chad McWilliams


Chad,

You might use -r on the command line you are calling with "system" to
pass the user id to the program you are firing up with "system".  Then
in the program you are calling with "system" look at @pm.  If there is a
value in it, then use that as the user id to do your lookup of what's
authorized.  If there is no value in @pm then that means the program was
not fired up by a "system" call but perhaps was started from a user
menu.  In that case, use the normal @id to get the user id.

Regards,

Scott