Sponsored Content
Top Forums UNIX for Advanced & Expert Users sudo wildcards problem: for every argument a *-wildcard? Better solution? Post 302557026 by slashdotweenie on Tuesday 20th of September 2011 10:12:01 AM
Old 09-20-2011
Quote:
Originally Posted by vbe
What have you in sudoers files?
Sudoers is in LDAP. See sudoCommand in original posting

Sudoers LDAP Manual

Quote:
Originally Posted by vbe
I suppose you would need something like:
Code:
/app/appname/connectors/*/*/current/bin/* *

So that it accept all arguments...
works only with one argument. Doesn't work.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Find wildcard .shtml files in wildcard directories and removing them- How's it done?

I'm trying to figure out how to build a small shell script that will find old .shtml files in every /tgp/ directory on the server and delete them if they are older than 10 days... The structure of the paths are like this: /home/domains/www.domain2.com/tgp/ /home/domains/www.domain3.com/tgp/... (1 Reply)
Discussion started by: Neko
1 Replies

2. UNIX for Dummies Questions & Answers

how to check if the argument contain wildcard (*,?) ?

In a script , i would like to check if the argument ( $1, $2 inside the script) contain wildcard (*,? etc). how do i do it? > script_name arg1 arg* $1 (arg1) does not contain wildcard, but $2 (arg* )contains wildcard. how can i tell in script? i need to do this is because : if arg1... (3 Replies)
Discussion started by: gusla
3 Replies

3. Solaris

Problem in using wildcard characters in xargs with find

Hi, Under my parent diectory I have directory named "Response" in many of its subfolders. I am interested to see all files with extention .pro in Response Directory. I am giving following command - find . -name "Response" -type d | xargs -i ls -lrt {}/*.pro but it is not giving result. ... (3 Replies)
Discussion started by: sanjay1979
3 Replies

4. Shell Programming and Scripting

Problem when concatinating wildcard onto file location in bash script

I am having difficulty with the following script: #! /bin/bash filelist=~/data/${1}* ~/./convertFile $filelist ~/temp/outputEssentially, there are a large number of files in the directory ~/data, each with a four-letter code at the beginning (eg. aaaa001 aaaa002 bbbb001 bbbb002 etc). The... (11 Replies)
Discussion started by: Lears_Fool
11 Replies

5. UNIX for Dummies Questions & Answers

Problem with use of the ? wildcard in regex substitution.

I'm trying to use Larry Wall's rename (prename) tool to rename multiple files: $ ls -1 blar.m4mp3 BLAH.mpmp3 bar foo.m4mp3 foo bar.mpmp3 I'm trying to fix the extensions so they're all .mp3: rename 's/m?mp3/mp3/' *mp3 I expect m?mp3 to match the extensions,... (3 Replies)
Discussion started by: ropers
3 Replies

6. Shell Programming and Scripting

Wildcard in mailx argument

Hi All, I have to send some files as attachments to an email using mailx copmmand in a shell script. The files will be generated by some other application everyday with names starting with the literal 'Send' followed by some random sequence of characters in the filenames. I tried... (1 Reply)
Discussion started by: sagarparadkar
1 Replies
XCODE-SELECT(1) 					    BSD General Commands Manual 					   XCODE-SELECT(1)

NAME
xcode-select - Manages the active developer directory for Xcode and BSD tools. SYNOPSIS
xcode-select [-h|--help] [-s|--switch <path>] [-p|--print-path] [-v|--version] DESCRIPTION
xcode-select controls the location of the developer directory used by xcrun(1), xcodebuild(1), cc(1), and other Xcode and BSD development tools. This also controls the locations that are searched for by man(1) for developer tool manpages. This allows you to easily switch between different versions of the Xcode tools and can be used to update the path to the Xcode if it is moved after installation. Usage When multiple Xcode applications are installed on a system (e.g. /Applications/Xcode.app, containing the latest Xcode, and /Applica- tions/Xcode-beta.app containing a beta) use xcode-select --switch path/to/Xcode.app to specify the Xcode that you wish to use for command line developer tools. After setting a developer directory, all of the xcode-select provided developer tool shims (see FILES) will automatically invoke the ver- sion of the tool inside the selected developer directory. Your own scripts, makefiles, and other tools can also use xcrun(1) to easily lookup tools inside the active developer directory, making it easy to switch them between different versions of the Xcode tools and allow- ing them to function properly on systems where the Xcode application has been installed to a non-default location. OPTIONS
-h, --help Prints the usage message. -s <path>, --switch <path> Sets the active developer directory to the given path, for example /Applications/Xcode-beta.app. This command must be run with supe- ruser permissions (see sudo(8)), and will affect all users on the system. To set the path without superuser permissions or only for the current shell session, use the DEVELOPER_DIR environment variable instead (see ENVIRONMENT). -p, --print-path Prints the path to the currently selected developer directory. This is useful for inspection, but scripts and other tools should use xcrun(1) to locate tool inside the active developer directory. -r, --reset Unsets any user-specified developer directory, so that the developer directory will be found via the default search mechanism. This command must be run with superuser permissions (see sudo(8)), and will affect all users on the system. -v, --version Prints xcode-select version information. --install Opens a user interface dialog to request automatic installation of the command line developer tools. ENVIRONMENT
DEVELOPER_DIR Overrides the active developer directory. When DEVELOPER_DIR is set, its value will be used instead of the system-wide active developer directory. Note that for historical reason, the developer directory is considered to be the Developer content directory inside the Xcode applica- tion (for example /Applications/Xcode.app/Contents/Developer). You can set the environment variable to either the actual Developer con- tents directory, or the Xcode application directory -- the xcode-select provided shims will automatically convert the environment vari- able into the full Developer content path. EXAMPLES
xcode-select --switch /Applications/Xcode.app/Contents/Developer Select /Applications/Xcode.app/Contents/Developer as the active developer directory. xcode-select --switch /Applications/Xcode.app As above, selects /Applications/Xcode.app/Contents/Developer as the active developer directory. The Developer content directory is auto- matically inferred by xcode-select. /usr/bin/xcodebuild Runs xcodebuild out of the active developer directory. /usr/bin/xcrun --find xcodebuild Use xcrun to locate xcodebuild inside the active developer directory. env DEVELOPER_DIR="/Applications/Xcode-beta.app" /usr/bin/xcodebuild Execute xcodebuild using an alternate developer directory. FILES
/usr/bin/xcrun Used to find or run arbitrary commands from the active developer directory. See xcrun(1) for more information. /usr/bin/actool /usr/bin/agvtool /usr/bin/desdp /usr/bin/genstrings /usr/bin/ibtool /usr/bin/ictool /usr/bin/instruments /usr/bin/iprofiler /usr/bin/opendiff /usr/bin/sdef /usr/bin/sdp /usr/bin/stapler /usr/bin/xcodebuild /usr/bin/xed Runs the matching Xcode tool from with the active developer directory. /usr/bin/BuildStrings /usr/bin/CpMac /usr/bin/DeRez /usr/bin/GetFileInfo /usr/bin/MergePef /usr/bin/MvMac /usr/bin/ResMerger /usr/bin/RezDet /usr/bin/RezWack /usr/bin/Rez /usr/bin/SetFile /usr/bin/SplitForks /usr/bin/UnRezWack /usr/bin/ar /usr/bin/as /usr/bin/asa /usr/bin/bison /usr/bin/c89 /usr/bin/c99 /usr/bin/clang++ /usr/bin/clang /usr/bin/cmpdylib /usr/bin/codesign_allocate /usr/bin/cpp /usr/bin/ctags /usr/bin/ctf_insert /usr/bin/dsymutil /usr/bin/dwarfdump /usr/bin/flex++ /usr/bin/flex /usr/bin/g++ /usr/bin/gatherheaderdoc /usr/bin/gcc /usr/bin/gcov /usr/bin/git-cvsserver /usr/bin/git-receive-pack /usr/bin/git-shell /usr/bin/git-upload-archive /usr/bin/git-upload-pack /usr/bin/git /usr/bin/gm4 /usr/bin/gnumake /usr/bin/gperf /usr/bin/hdxml2manxml /usr/bin/headerdoc2html /usr/bin/indent /usr/bin/install_name_tool /usr/bin/ld /usr/bin/lex /usr/bin/libtool /usr/bin/lipo /usr/bin/lldb /usr/bin/lorder /usr/bin/m4 /usr/bin/make /usr/bin/mig /usr/bin/mkdep /usr/bin/nasm /usr/bin/ndisasm /usr/bin/nm /usr/bin/nmedit /usr/bin/objdump /usr/bin/otool /usr/bin/pagestuff /usr/bin/ranlib /usr/bin/rebase /usr/bin/redo_prebinding /usr/bin/resolveLinks /usr/bin/rpcgen /usr/bin/segedit /usr/bin/size /usr/bin/strings /usr/bin/strip /usr/bin/svn /usr/bin/svnadmin /usr/bin/svndumpfilter /usr/bin/svnlook /usr/bin/svnserve /usr/bin/svnsync /usr/bin/svnversion /usr/bin/swift /usr/bin/swiftc /usr/bin/unifdef /usr/bin/unifdefall /usr/bin/xml2man /usr/bin/yacc Runs the matching BSD tool from with the active developer directory. SEE ALSO
xcrun(1), xcodebuild(1) HISTORY
The xcode-select command first appeared in Xcode 3.0. Mac OS X March 08, 2016 XCODE-SELECT(1)
All times are GMT -4. The time now is 07:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy