You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
Original issue 17 created by takahashi.shuhei on 2010-11-04T16:41:28.000Z:
"make install" invokes sudo to install PAM modules to /lib/security, but this is really bad behavior.
You should instruct users to type "sudo make install" instead, or just removing "sudo" is okay since it's a common manner to do that.
Reproduced in current hg head (74cba81d48).
The text was updated successfully, but these errors were encountered:
I agree with this report. The current behaviour was very much unexpected; I don't expect processes to run with root privileges unless I specifically say so.
(not to mention the minor issue that not all my systems have sudo installed, so make install presumably will error out on these systems even though I might already have root privileges).
Comment #4 originally posted by vivek@khera.org on 2011-03-10T14:02:27.000Z:
That fix doesn't really address the issue. The user should invoke sudo on the make, not just be warned it is going to be invoked for them. It is just bad form to invoke sudo from within the makefile itself.
Original issue 17 created by takahashi.shuhei on 2010-11-04T16:41:28.000Z:
"make install" invokes sudo to install PAM modules to /lib/security, but this is really bad behavior.
You should instruct users to type "sudo make install" instead, or just removing "sudo" is okay since it's a common manner to do that.
Reproduced in current hg head (74cba81d48).
The text was updated successfully, but these errors were encountered: