Re: setting the sticky bit on sqlexec

In article <BKUHN.93Jun8094629@rhlab.rhlab.UUCP>, bkuhn@rhlab.rhlab.UUCP (bmk Bradley Kuhn) writes: |> Since users are constantly firing up sqlexec engine processes when running |> database applications, I thought that it might be useful for system |> performance to set the sticky bit on the sqlexec binary. Has anyone every |> tried this? I don't have experience with SYSVR3, but if the sticky bit behaves in the usual way, then it probably won't have much effect. The sticky bit is useful when repeated executions of a program don't overlap in time. In most database environments, I would guess, there are at least some users who run data-entry applications for long periods, and while they're doing that, sqlexec is loaded. Assuming sqlexec is sharable, a user starting another application will just link to that copy, even without the sticky bit being set. (If it isn't sharable, I don't think the sticky bit has any effect.) Setting this bit would be useful if most of your applications run for short periods of time, so that it's often the case that you start a database application while there aren't any others running |> I am weary of doing this in fear that it may screw something up. |> Any info would be appreciated. Setting the sticky on LOTS of programs could conceivably contribute to running out of swap space. Otherwise it should be safe, I think. But remember, I don't know your version of Unix :-( Good Luck, -- Harry Bochner bochner@das.harvard.edu