Hello everybody,
My question is: how to add /tmp/work at the end of line in vi editor.
my file looks like:
cp file1
cp file2
cp file3
****
I need to add " /tmp/work" at the end of each line.
I tried this
:%s/$/" /tmp/work"
and this
:%s/$/\ /tmp/work\/
but it does not work. (2 Replies)
Hi,
how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before.
for exemple if in my file i have
line 1
line 2
I want to have :
start line 1 end
start line 2 end (3 Replies)
I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work.
how can I enable them.
thanks (3 Replies)
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Hello All,
Need one Help for one issue.
I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it.
It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
I was looking through the topics and I wasn't sure if this was the best place to post this question:
I was wondering, out of curiosity, which software everyone was using to code their scripts in. I do mostly sh/ksh and my favorite has always been EditPlus because it is small, fast, yet powerful.... (409 Replies)
Discussion started by: yongho
409 Replies
LEARN ABOUT CENTOS
__pmspeclocalpmda
PMSPECLOCALPMDA(3) Library Functions Manual PMSPECLOCALPMDA(3)NAME
__pmSpecLocalPMDA - process command-line argument for the table of DSO PMDAs
C SYNOPSIS
#include <pcp/pmapi.h>
#include <pcp/impl.h>
char *__pmSpecLocalPMDA(const char *spec);
cc ... -lpcp
DESCRIPTION
PCP contexts of type PM_CONTEXT_LOCAL are used by clients that wish to fetch metrics directly from one or more PMDAs on the local host
without involving pmcd(1).
__pmSpecLocalPMDA provides a convenience wrapper to be used by applications that wish to use a command line argument (usually with -K) to
control the DSO PMDAs that are available for a PM_CONTEXT_LOCAL context.
The spec argument specifies actions for one or more DSO PMDAs using up to four fields separated by commas (``,''), namely:
- an opcode with one of the values add (add a new entry), del (delete an existing entry) or clear (clear all entries from the table).
- the PMDA's domain number
- the path to the PMDA DSO (may be absolute or relative to the $PCP_VAR_DIR/pmdas directory and the DSO suffix is optional), and
- the name of the PMDA's initialization routine.
All fields are required to add a new entry. To delete an entry the opcode is required plus either or both of the domain number and path
fields. To clear all entries, only the opcode is required.
If spec is parsed successfully, then __pmLocalPMDA(3) is called with the extracted arguments.
RETURN VALUE
On success, __pmSpecLocalPMDA will return NULL.
On error or failure, __pmSpecLocalPMDA will return a pointer to a static error message.
EXAMPLES
Some examples of valid spec strings:
clear Delete all entries from the DSO table.
add,123,foo/foo_pmda,foo_init
Add the ``foo'' PMDA using domain 123. The PMDA's DSO is most likely in below the directory $PCP_PMDAS_DIR and named
foo/foo_pmda.so (for ELF-style platforms) or foo/foo_pmda.dylib (for BSD-style platforms) or fooo_pmda.dll (for Windows-style plat-
forms). The initialization routine for the ``foo'' PMDA is foo_init().
del,123
Delete the entry for the DSO with domain 123.
del,,foo/foo_pmda
Delete the entry with a pathname to the DSO that matches foo/foo_pmda.
del,123,foo/foo_pmda
Delete the entry for the DSO with either domain 123 and/or a pathname to the DSO that matches foo/foo_pmda.
SEE ALSO PMAPI(3), __pmLocalPMDA(3) and pmNewContext(3).
Performance Co-PilotPMSPECLOCALPMDA(3)