Topic: PFROOTFIX=OFF

[kenbrody]

PFROOTFIX=OFF

Starting with filePro 5.0.12, there was a slight change in how filePro runs if you are running as id "root".  Setting PFROOTFIX=OFF restores the old behavior.

So... what, exactly, is the new behavior?

On some newer versions of Unix and Linux (as well as all versions of AIX, as far as I know), there is a security feature which prevents a program which is running as UID "root", and an effective UID of something else, from spawning child processes.

In other words, filePro would not be able to execute SYSTEM commands, nor any USER commands, nor could it open the spooler to print.

The change in 5.0.12 causes filePro, when run as real UID "root" to give up its root privileges and switch its real UID (not just the effective UID) to "filepro".

How does this affect things?

Within filePro, there is basically no change.  However, any child processes that may be spanwed (such as via SYSTEM, USER, or printing) will now be running as uid "filepro" rather than "root".

If you have banners enabled on printing, it may print "filepro" rather than "root" as the owner.

If your SYSTEM or USER programs require root privileges, they will no longer run, as they are running as UID "filepro".

If you SYSTEM out to another filePro program, @ID will be "filepro" rather than "root".

What if you need child processes to be UID "root"?

By setting PFROOTFIX=OFF, you will retore the old behavior, where filePro will still be running as UID "root" and EUID "filepro".

However, if you are on one of the systems that require the fix, you must not set PFROOTFIX=OFF, as that will prevent filePro from running any SYSTEM or USER commands, or openning the print spooler.

Note:

Remember, however, that this only affects you if you are running as "root".  It will have no effect on any non-root users.