that was my point, easier to remember that +s is that sticky is easier to remember or associate with +s. Also, unless i don't understand what an OS is, this program (port.status) is not part of the OS but part of the DB. I too would not be doing this to an OS program.
On Thu, Sep 4, 2008 at 6:58 AM, jpb-u2ug <[EMAIL PROTECTED]> wrote: > My mistake, thanks Ken. It's just that when you don't do it too often the > names get jumbled together. Beside the fact that '+s' sounds like it should > be sticky. > > Jerry Banker > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis > Sent: Wednesday, September 03, 2008 10:04 PM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] port.status > > OK, I ignored it the first time, but if this is going to keep rolling then > I > need to jump in with a correction before people assume it must be correct. > > This is not the 'sticky' bit. The purpose of the sticky bit on some > (older) > unix implementations is to keep the text segment of an executable loaded in > memory once it has been executed rather than unloading it at completion. > This was designed to make commonly used programs load faster, but is now > pretty much irrelevant in that context and is ignored by some unix > implementations such as Linux. The sticky bit is most often used now on > directories such as /tmp where it requires the actual owner of a file to > delete or modify that file, even though other users might have write > permission on the directory. The sticky bit gets set with chmod +t. > > If you want a program to run with the credentials of another user (such as > root) when it is executed, then you set the 'setuid' bit with chmod +s and > make sure the file is owned by the appropriate user and executable by > relevant people. > > I won't get into arguments about how good an idea it is to set the setuid > bit on random bits of the operating system. > > Cheers, > > Ken > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of JPB-U2UG > Sent: Thursday, 4 September 2008 11:24 AM > To: u2-users@listserver.u2ug.org > Subject: Re: [U2] port.status > > Yes, but it should have already been set. If you want it to work with > everyone then set the sticky bit in the /usr/bin/ipcs. > > -------------------------------------------------- > From: "Lloyd Cottrell" <[EMAIL PROTECTED]> > Sent: Wednesday, September 03, 2008 12:19 PM > To: <u2-users@listserver.u2ug.org> > Subject: Re: [U2] port.status > > > i've found that you need to flip on the sticky bit on the list_readu > > program > > to fix this problem, which makes it run as root > > > > On Tue, Sep 2, 2008 at 2:49 PM, <[EMAIL PROTECTED]> wrote: > > > >> New install of Universe 10.2.4 > >> >PORT.STATUS > >> There are no uniVerse sessions that match the specified conditions. > >> > >> But one user is logged on as root and then starting /usr/ibm/uv/bin/uv. > >> And is running a multple program jobstream, so something Universe > should > >> have been detected. > >> > >> And we get the same results if a user logins with a unique login, is > then > >> pointed to the /bin/ksh and starting uv. > >> > >> Thanks. > >> Roger > >> ------- > >> 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/ > ------- > 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/
