Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #7104
| From | Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Case insensitive bash search? |
| Date | 2013-01-25 16:14 -0800 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <kdv74q$5oo$1@speranza.aioe.org> (permalink) |
| References | (1 earlier) <1KzMs.131493$2v.110871@newsfe05.iad> <87r4l982oa.fsf@araminta.anjou.terraraq.org.uk> <amg980F91h0U3@mid.individual.net> <kdv2mc$s28$1@speranza.aioe.org> <kdv4fh$c1$1@speranza.aioe.org> |
On 01/25/2013 03:28 PM, Jon Danniken wrote: > > Okay, so I made the following script for this, and called it "xx": > > #! /bin/bash > ls -l | grep -i $1 > > And it works for my user, by invoking it as ./xx > > So now I put it into /usr/bin, so that I can avoid the leading "./", but > I have to use sudo to run it, despite having the proper permissions: > > [root@FED bin]# pwd > /usr/bin > [root@FED bin]# ll xx > -rwx--x--x. 1 root root 37 Jan 25 15:22 xx > > Any ideas why I have to run this as root or sudo? After taking a nap on this, it dawned on me that my user would have to read the script before executing the script, so adding read permission to the script allows my normal user to run it: [user@FED bin]$ pwd /usr/local/bin [user@FED bin]$ ll -rwxr-xr-x. 1 root root 42 Jan 25 16:01 xx Thanks again for all the help! Jon
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Case insensitive bash search? Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> - 2013-01-25 08:59 -0800
Re: Case insensitive bash search? Robert Heller <heller@deepsoft.com> - 2013-01-25 11:44 -0600
Re: Case insensitive bash search? gazelle@shell.xmission.com (Kenny McCormack) - 2013-01-29 13:56 +0000
Re: Case insensitive bash search? Wayne <nospam@all.invalid> - 2013-01-29 12:41 -0500
Re: Case insensitive bash search? unruh <unruh@invalid.ca> - 2013-01-25 17:59 +0000
Re: Case insensitive bash search? Lew Pitcher <lpitcher@teksavvy.com> - 2013-01-25 13:13 -0500
Re: Case insensitive bash search? Lew Pitcher <lpitcher@teksavvy.com> - 2013-01-25 13:23 -0500
Re: Case insensitive bash search? Richard Kettlewell <rjk@greenend.org.uk> - 2013-01-25 19:48 +0000
Re: Case insensitive bash search? ray carter <ray@zianet.com> - 2013-01-25 20:45 +0000
Re: Case insensitive bash search? Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> - 2013-01-25 14:58 -0800
Re: Case insensitive bash search? Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> - 2013-01-25 15:28 -0800
Re: Case insensitive bash search? Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> - 2013-01-25 16:14 -0800
Re: Case insensitive bash search? Robert Heller <heller@deepsoft.com> - 2013-01-25 19:04 -0600
Re: Case insensitive bash search? unruh <unruh@invalid.ca> - 2013-01-26 06:51 +0000
Re: Case insensitive bash search? unruh <unruh@invalid.ca> - 2013-01-26 06:47 +0000
Re: Case insensitive bash search? unruh <unruh@invalid.ca> - 2013-01-26 16:36 +0000
Re: Case insensitive bash search? Tim Watts <tw+usenet@dionic.net> - 2013-01-25 20:01 +0000
Re: Case insensitive bash search? Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> - 2013-01-25 15:01 -0800
Re: Case insensitive bash search? Tim Watts <tw+usenet@dionic.net> - 2013-01-25 23:36 +0000
Re: Case insensitive bash search? Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> - 2013-01-25 16:09 -0800
Re: Case insensitive bash search? Tim Watts <tw+usenet@dionic.net> - 2013-01-26 11:21 +0000
Re: Case insensitive bash search? Jon Danniken <jonSPAMdanniken@yaSMPAhoo.com> - 2013-01-26 15:14 -0800
Re: Case insensitive bash search? "Chris F.A. Johnson" <cfajohnson@gmail.com> - 2013-01-25 20:11 -0500
csiph-web