11-06-2005
Why is it Bad Idea to insert "." (Dot) to PATH ?
I was told that it's a Bad Idea (especially for root ) to Add To the Variable $PATH in unix the ":." (dot),
In order to execute programs in my current directory without typing ./program
For example: PATH=$PATH:$HOME/bin:.
Does someone know why is it a Bad Idea?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
When I try to run a script with ". "(dot space) in my home, it gives me error ".: Permission denied".
Any explanation for this behaviour?
Thanks in advance,
-Ashish (3 Replies)
Discussion started by: shriashishpatil
3 Replies
2. Shell Programming and Scripting
Hallo,
i need a Prompting read in my script:
read -p "Enter your command: " command
But i always get this Error:
-p: is not an identifier
When I run these in c-shell i get this error
/usr/bin/read: read: bad option(s)
How can I use a Prompt in the read command? (9 Replies)
Discussion started by: wiseguy
9 Replies
3. Shell Programming and Scripting
I had the idea come into my head that it would be good to have a single command that gave file type, file size, last modification date, and owner/group information, like what one would see in a GUI "Properties" dialog, but all in a terminal window. In my opinion, these statistics about a file... (5 Replies)
Discussion started by: SilversleevesX
5 Replies
4. Shell Programming and Scripting
Hi
I have a "set" command which ends with a "." (dot), for example:
set `grep "\<${pnum}\>" /tstmp/data.txt |sed 's/#//'` .
Can somebody help me to understand the purpose of this "set" and "." combination?
The problem is that this command does not produce the same result when run on AIX... (2 Replies)
Discussion started by: aoussenko
2 Replies
5. Shell Programming and Scripting
hello,
I am writting a regular expression that intend to match any tunnel or serial interface but it doesn't mtach any serial sub-interface.
For example, statement should match "Tunnel3" or "Serial0/1" but shouldn't match "Serial0\1.1" (doesn't include dot ".")
I tried the following but... (3 Replies)
Discussion started by: ahmed_zaher
3 Replies
6. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
7. Shell Programming and Scripting
If I enter (simplified):
find . -printf "%p\n"
then all files in the output are prepended by a "." like
./local/share/test23.log
How can achieve that
a.) the leading "./" is omitted
and/or
b.) the full path to the current directory is inserted (enclosed by brackets and a blank)... (1 Reply)
Discussion started by: pstein
1 Replies
8. Shell Programming and Scripting
Hi,
I'm dealing with an issue and losing a lot of hours figuring out how i would solve this.
I have an input file which looks like this:
('BLABLA +200-GRS','Serviço ','TarifaçãoServiço','wap.bla.us.0000000121',2985,0,55,' de conversão em escada','Dia','Domingos')
('BLABLA +200-GRR','Serviço... (6 Replies)
Discussion started by: poliver
6 Replies
9. Shell Programming and Scripting
Hello.
Following recommendations for one of my threads, this is working perfectly :
#!/bin/bash
CNT=$( grep -c -e "some text 1" -e "some text 2" -e "some text 3" "/tmp/log_file.txt" )
Now I need a grep success for some thing like :
#!/bin/bash
CNT=$( grep -c -e "some text_1... (4 Replies)
Discussion started by: jcdole
4 Replies
10. Shell Programming and Scripting
These three finds worked as expected:
$ find . -iname "*.PDF"
$ find . -iname "*.PDF" \( ! -name "*_nobackup.*" \)
$ find . -path "*_nobackup*" -prune -iname "*.PDF"
They all returned the match:
./folder/file.pdf
:b:
This find returned no matches:
$ find . -path "*_nobackup*" -prune... (3 Replies)
Discussion started by: wolfv
3 Replies
LEARN ABOUT PLAN9
filecap
FILECAP:(8) System Administration Utilities FILECAP:(8)
NAME
filecap - a program to see capabilities
SYNOPSIS
filecap [ -a | -d | /dir | /dir/file [cap1 cap2 ...] ]
DESCRIPTION
filecap is a program that prints out a report of programs with file based capabilities. If a file is not in the report or there is no
report at all, no capabilities were found. For expedience, the default is to check only the directories in the PATH environmental variable.
If the -a command line option is given, then all directories will be checked. If a directory is passed, it will recursively check that
directory. If a path to a file is given, it will only check that file. If the path to the file includes capabilities, then they are written
to the file.
OPTIONS
-a This tells the program to show all capabilities starting from the / directory. Normally the PATH environmental variable is used to
show you capabilities on files you are likely to execute.
-d This dumps all capabilities for reference.
EXAMPLES
To check file capabilities in $PATH:
filecap
To check file capabilities of whole system:
filecap -a
To check file capabilities recursively in a directory:
filecap /usr
To check file capabilities of a specific program:
filecap /bin/passwd
To list all possible capabilities:
filecap -d
To set a file capability on a specific program:
filecap /bin/ping net_raw net_admin
SEE ALSO
pscap(8), netcap(8), capabilities(7).
AUTHOR
Steve Grubb
Red Hat March 2009 FILECAP:(8)