For what it is worth, the reason pref (or any other program that uses the OM) must have root permissions is that it accesses a shared memory segment used by the OM. This segment has permissions on it and root is the only user. By setting the set-uid bit, you are telling the OS to run the program as if it were invoked by the owner of the program rather than the user of the program. Make sense? Regards, Alex Johnson Invensys Systems, Inc. 10707 Haddington Houston, TX 77043 713.722.2859 (voice) 713.722.2700 (operator) 713.932.0222 (fax) ajohnson@xxxxxxxxxxx For the latest information on ArchestrA, go to http://www.invensys.com/Archestra.html. -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Brian Bates Sent: Thursday, July 29, 2004 7:56 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] shut down DM from a script Thanks Duc (and Jeremy). I used chmod +s, and now it works. -Brian. duc.do@dowcorning .com To: foxboro@xxxxxxxxxxxxx Sent by: cc: foxboro-bounce@fr Subject: Re: [foxboro] shut down DM from a script eelists.org 07/28/2004 03:38 PM Please respond to foxboro I change the setUID permission of pref (chmod +s /usr/local/pref, run as root) and I can issue the dmexit as a user other than root. Disclaimer: There's no guarantee that this change doesn't break anything. Use at your own risk. Duc -- Duc M. Do Dow Corning Corp. Carrollton Plant Carrollton, KY, US -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Brian Bates Sent: Wednesday, July 28, 2004 3:27 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] shut down DM from a script Terry. Both DMCMD and dmcmd will work, - if you are logged in as root. If you are logged in as a non-root user, it doesn't work either way. This surprises me because by the looks of it, pref should be executable by anybody, if I am reading this properly. # ls -l /usr/local/pref -rwxr-xr-x 1 root staff 7264 Jun 24 1998 /usr/local/pref -Brian _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave