On Fri, May 16, 2014 at 10:07 AM, Howard White <[email protected]> wrote: > Could someone give me a short course on why it is one executes these steps: > > ./configure as root > make as a user > make install as root > > ???? > > I'm confused... > > Howard
You don't necessarily need to run configure as root, but there are some tests, especially for daemons which start as root, which need the additional privileges to execute. For example, in Asterisk, I've written a test to check whether one may provide a bitfield longer than 1024 bits to the select(2) kernel call. This functionality is necessary to see if we can practically have more than 1024 file handles open, or if things would simply not work in that case. The problem is that you cannot have a file handle numbered greater than 1023 by default in any process, so you have to increase the available number of file handles in order to run that test. I realize that is a very technical answer, but you have to understand the purpose of the test in order to understand why it's necessary sometimes to run as root. In terms of the compile process, that could just as easily run as root as the user, but you should definitely always run something with the least privilege necessary to get the job done, and in terms of the compile, root privileges are not necessary. -- Tilghman -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
