Jump to content

Search the Community

Showing results for tags 'sudo'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Categories

  • New Features
  • Other

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 2 results

  1. My goal is to automate the process of updating a user's hosts file. (/etc/hosts/) I have a bash script that works fine if I run it from my home directory. User opens Alfred and types in the keyword "hostsup" (No arguments required) Alfred opens a Terminal window and runs a script that has been added to the Workflow folder The script displays some informative text for the user Then the scripts ask the user if they would like to continue On 'y', the terminal prompts the user for their password (Because the command uses sudo) The script outputs a completion message and instructs the user to close the Terminal window If I use "Keyword to Script", I can embed the script as part of the Workflow and run it, but it does not run interactively, so the user receives no prompts or messages. If I use "Keyword to Terminal Command", I can run a simple bash "one-liner", but I can't figure out how to call the script that I've included in the Workflow folder. Any help would be greatly appreciated.
  2. From the README.md First: avoid, at all costs, adding a sudo entry. Only add an entry to your sudoers file as a last resort. If you do need to add an entry, however, this is a great way to do it because it will check your syntax with visudo, making sure that you do not break your sudoers file (which is really, really bad). Also included is "which" command that allows you to grab the path of the command you need to add to the sudoers file. Hence, just invoke "which <command_name>" and the path will be copied to your clipboard. After that, type "addsudo" — no arguments. You'll be prompted to put in your password. Do that to be able to edit the file. Then, there will be a dialog box that pops up. Just paste the command here and add any arguments that you need. If the command is valid, then it will write a line to the file that will give the current user permissions to use that command without a password (here, obviously is the potential security threat that makes adding a line to the file a last resort). The nice thing about this workflow is that it will not let you break your sudoers file. So if you aren't familiar with the syntax but need to add an entry, then use this rather than trying to edit it yourself. Github repo Direct Download here Screenshots:
×
×
  • Create New...