I have a problem with the script below
#!/bin/sh
for vo in `find -maxdepth 1 -type f -regex "^\./*$"`
do
ls -l "$vo"
some other commands
done
It works fine until `find ...` returns files with spaces. I've tryed to change IFS but haven't succeed
Any solutions? (4 Replies)
I'm trying to do something like that:
for $filename in `ls -1`
do
some_command $filename
done
but it doesn't work properly for file names with spaces, for...in splits at spaces. Anyway around? (4 Replies)
I have files on my unix boxes that users have created with spaces.
Example: /tmp/project plan
ls -l "/tmp/project plan" works fine.
$/tmp>ls -l "/tmp/project plan"
-rw-r--r-- 1 root other 0 Jan 31 12:32 /tmp/project plan
I created a file called test and put just the... (2 Replies)
Hi All,
I see similar problems in past threads but so far no answers have worked for me. I am trying to write a script which parses a txt file that contains one filename per line, then finds those files on the local disk and copies them to a specified directory.
What I have:
... (4 Replies)
Hi,
I want to list all the files matching in a directory directory given below
Here one of the folder has a space in the path.
/MAS02/RMS/WBDev/Krishna/Krishna Mohan/FMSplitByKeyAfterChanges1000075383.fileman.*.txt.out.1000075383.0
The following works from command line... (1 Reply)
Hi
I hope someone will be able to resolve this little teaser!
I am running a script
for file in `ls directory`
do
echo "$file"
...other code here....
done
this works fine unless we receive a file with a name which has a space in it
ie
"filena me"
(I know its not good... (8 Replies)
I want to ftp all the sh files in the directory. Also if any of the file name
contains spaces in them, it should be converted to underscores before it is ftped. I wrote the following code below:
FILESSH=$(ls /mysh/*.sh)
--- FILESH being used here for some other task ---
echo "$FILESSH" |... (3 Replies)
Hey there, this is my first post and I'll try to explain my situation as best I can.Here is a sample of the input file:
ADO Sample.h,v ADO Sample 2010-05-21 lyonsb /repository/patents/TSCommon/OpenSource/Dundass/ug6mfc/DataSources/Ado/ADO Sample
ADO SampleDoc.h,v ADO SampleDoc 2010-05-21... (3 Replies)
Hi all,
I've a requirement as below
Source file src.txt sample data:
A<10 white spaces>B12<5 white spaces>C<17 white spaces>
A1<5 white spaces>B22<5 white spaces>C13<17 white spaces>
when I'm fetching a record from this file into a shell variable like below:
vRec=`head -1 src.txt... (2 Replies)
I'm trying to handle some files with spaces in their name using "" or \ . Like "file 1" or file\ 1.
My current confusion can be expressed by the following shell script:
#!/bin/bash
touch "file 1" "file 2"
echo -n "ls: " ; ls
echo ---
for file in "file 1" "file 2" ; do
echo $file... (9 Replies)
Discussion started by: Ralph
9 Replies
LEARN ABOUT CENTOS
pcp.conf
PCP.CONF(5) File Formats Manual PCP.CONF(5)NAME
pcp.conf - the Performance Co-Pilot configuration and environment file
SYNOPSIS
/etc/pcp.conf
DESCRIPTION
When using Performance Co-Pilot (PCP) tools and utilities and when calling PCP library functions, a standard set of environment variables
are defined in /etc/pcp.conf. These variables are generally used to specify the location of various PCP pieces in the file system and may
be loaded into shell scripts by sourcing the /etc/pcp.env(5) shell script and queried by C/C++ programs using the pmGetConfig(3) library
function. If a variable is already defined in the environment, the values in pcp.conf do not override those values, i.e. the values in
pcp.conf serve as installation defaults only.
Both the pcp.env and pcp.conf files are expected to be found in /etc by default. If required, the pcp.conf file may be relocated and
PCP_CONF set in the environment to specify the full path to the new location. The pcp.env file can not be relocated (this is the only hard
coded path required by PCP).
The syntax rules for pcp.conf are as follows :
1. the general syntax is
PCP_VARIABLE_NAME=variable value to end of line
2. lines that begin with # and all blank lines are ignored.
3. all variables must be prefixed with PCP_. This is a security issue - variables that do not have this prefix will be silently ignored.
4. there should be no space between the variable name and the literal = and no space between the = and the variable value (unless the
value actually starts with a space). This is required because the pcp.conf file may be sourced directly by Makefiles as well as inter-
preted by the pcp.env script and the pmGetConfig function.
5. variable values may contain spaces and should not be quoted. The pcp.env script automatically quotes all variable values from the
character immediately following the = through to the end of the line.
For further details and an explanation of the use of each variable, see the comments in the /etc/pcp.conf file itself.
ENVIRONMENT
The PCP_CONF environment variable specifies an alternative path to the pcp.conf file.
SEE ALSO PCPIntro(1), PCPIntro(3), PMAPI(3), pmGetConfig(3) and pcp.env(5).
Performance Co-Pilot PCP PCP.CONF(5)