FP & FreeBSD Revisited...
Chad McWilliams
chad at computiprint.com
Wed Jan 5 13:37:44 PST 2005
After some trials, here is some information some of you might find
useful, if using filepro on *bsd.
Problem:
When using the system command from within filepro, to run another
filepro process, the second process would run as filepro, not the logged
in user. Subsequently, any records created in the second process would
show filepro as the creator, not the user.
To some this may not be a problem, but if you use the @CB system field
for anything, it'll screw you up.
Solution:
When I brought this up originally, it was suggested I try using sudo to
see if I could get around the problem, which I did, and after getting
the sudoers file fixed, it seems to work well. So now, instead of a
line of code like this:
SYSTEM "/path/rclerk somefile -s0"
you would use the line:
SYSTEM "sudo -u"<@id<"/path/rclerk somefile -s0"
Anyway, just thought I would share the information with the group.
P.S. To me the way the SYSTEM command behaves under *bsd is a security
risk. If a user were to somehow get to a shell prompt while "SYSTEMed"
out, they would be able to do anything the filepro user would be able
to, including deleting the filepro files. This is in stark contrast to
the way SYSTEM behaves under SCO. I'm sure most of you realize this,
but I thought I would mention it for those it wasn't obvious to.
-Chad McWilliams
More information about the Filepro-list
mailing list