Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
remove sudo calls as script must be run as root #80
Conversation
|
Ping |
|
@psquickitjayant can you review this one? Probably good for you to watch this repo too. I noticed some formatting changes. |
|
@mostlyjason Hurray! Thanks for paying attention. :-) |
|
Ping |
|
sorry I missed it. I will check it now :) |
|
@psquickitjayant Ping |
|
@tmornini I have added this in my backlog. I am doing changes in the script. Once done, then will merge you changes. |
|
@psquickitjayant Are you joking? This has been outstanding since September! Why don't you merge the patch and rebase your changes atop master? |
|
How does this work for users who are not on EC2, for example if they are running as a non-root user on their own linux installation? It seems we need something that works for them too. If there is a way, we'd have to test it on other distributions too. Also, do we need the formatting changes? It seems better to follow a consistent standard. |
|
@mostlyjason Please read PR description again. This script REQUIRES that it be run as root. As such, there's zero need to use sudo. :-( |
|
@psquickitjayant is this deployed now? if so, we can close |
|
yes @mostlyjason |
|
@mostlyjason @psquickitjayant This repository is out-of-date, i.e. the Linux configure script does not match what's on Github, though it does include the removal of sudo as shown by this PR.
|
|
Wow, the script at https://www.loggly.com/install/configure-linux.sh not only differs with respect to sudo handling, but it entirely changes the semantics of the script in at least two ways:
|
|
@psquickitjayant can you test and confirm what @jmckee46 says? We want verification and the tags to work. |
|
@mostlyjason @jmckee46 APP_TAG is a property which is used by the other scripts like apache, tomcat, etc. It does not go for the verification steps if there are not any changes in the 22-loggly.conf file and it already exists. If you do a fresh install, or if there are any changes in 22-loggly.conf then verification steps run. |
|
We have already made the changes to remove the sudo from the script and make sure the script is run as root. |
|
Wow, fantastic, only took 1 month for first response and 7 months to close. And no merge, giving no credit or thanks for my pull request. You folks are truly living the open source dream! :-( |
|
@tmornini sorry about that! Thanks for your contribution! I think our forks are out of sync so we merged it in https://github.com/psquickitjayant/install-script. I'm not sure which commit it was in though. Hopefully we'll get this one synced up soon. Let us know if anything is missing. |
This patch eliminates:
exceptions when configuring Loggly via an AWS EC2 user data script.
Since
checkIfUserHasRootPrivileges()on https://github.com/loggly/install-script/blob/master/Linux%20Script/configure-linux.sh#L190 requires script to be run as root the use of sudo is entirely superfluous. :-)Until this patch is accepted, we're correcting in the user data script via: