Basically it's like this:
For the output file having the line numbers in it's name, I have no good short idea atm. Maybe someone else comes up with it or you try a bit too
We just recently moved from a DG-UX (Unix V) to HP 9000 servers running POSIX. I used the c-shell in the DG-UX system mainly because the bourne-shell did not support aliasing. Now in the default posix-shell of HP aliasing is supported. The main difference seams to be that in a c-shell you can pass... (1 Reply)
Hi all,
I'm trying to define an alias with an embeded awk command:
alias kpipe='kill `psme| grep "ifw -r" | grep -v "grep ifw -r"| awk '{print $2}'`'
The problem is that the awk command (awk '{print $2}') contains two ' ..' quotes. So bash assumes that the first awk quote corresponds to... (5 Replies)
Good morning
I would like kindly to ask you to help me with creation of alias with awk command.
alias a="awk {print $1 "| " $2 "| " $3 "| " $4 "| " $5 "| " $6 "| " $7 "| " $8 "| " $13 "| " }"
there is some error but I don't find it please explain me what is error and how can be avoid... (1 Reply)
Good morning
I would like kindly to ask you to help me with creation of alias with awk command.
alias a="awk {print $1 "| " $2 "| " $3 "| " $4 "| " $5 "| " $6 "| " $7 "| " $8 "| " $13 "| " }"
there is some error but I don't find it please explain me what is error and how can be avoid... (5 Replies)
I'd like to define an alias to awk's begin statement since I use awk with different delimiters all the time and it is tiresome to type awk '{OFS="\t";FS="\t"}{BLAH BLAH}' every time. The problem is that bash won't let me make an alias with an open quote, which is necessary for the BEGIN alias to... (3 Replies)
Is there a way to preform check if the parameters that was send with the command awk -f `file_name.awk` `input_file` before even it gets to the BEGIN section (i have tested a try to check in the BEGIN it doesn't let ,you must make it on the section that after the BEGIN) and then decide if the... (1 Reply)
Hi to all,
I'm facing some problems when adding an alias like:
#alias list="ls -al | awk '{ print $1, $2, $3, $4, (($5/1048576))"\t", $6, $7, $8, $9 }'"
and when I enter:
#list
I get:
Syntax Error The source line is 1.
The error context is
{ print >>> , <<<
awk:... (3 Replies)
I am trying to turn this into an alias with no luck. I would then like to put the alias into my bashrc file. I know awk is very picky about quotes. I have tried every version of quotes, single quotes, double quotes, and backslashes that I can think of.
VAR=$(xrandr | awk '$2=="connected"{s=$1}... (3 Replies)
Hi,
I am running the following df command to display df in GB. I am not able to use df -h on this server as that option is not available.
df -k /tmp | awk 'NR==1 {CNV=1024*1024;GBYTES="GBytes";FMT="%-35s %-10s %-10s %-10s %10s %-s\n"; printf FMT, $1, GBYTES, $3, $4, $5, $6; next} {printf... (3 Replies)
Discussion started by: newbie_01
3 Replies
LEARN ABOUT DEBIAN
logfetch
LOGFETCH(1) General Commands Manual LOGFETCH(1)NAME
logfetch - Xymon client data collector
SYNOPSIS
logfetch CONFIGFILE STATUSFILE
DESCRIPTION
logfetch is part of the Xymon client. It is responsible for collecting data from logfiles, and other file-related data, which is then sent
to the Xymon server for analysis.
logfetch uses a configuration file, which is automatically retrieved from the Xymon server. There is no configuration done locally. The
configuration file is usually stored in the $BBHOME/tmp/logfetch.cfg file, but editing this file has no effect since it is re-written with
data from the Xymon server each time the client runs.
logfetch stores information about what parts of the monitored logfiles have been processed already in the $BBHOME/tmp/logfetch.status file.
This file is an internal file used by logfetch, and should not be edited. If deleted, it will be re-created automatically.
SECURITY
logfetch needs read access to the logfiles it should monitor. If you configure monitoring of files or directories through the "file:" and
"dir:" entries in client-local.cfg(5) then logfetch will require at least read-acces to the directory where the file is located. If you
request checksum calculation for a file, then it must be readable by the Xymon client user.
Do NOT install logfetch as suid-root. There is no way that logfetch can check whether the configuration file it uses has been tampered
with, so installing logfetch with suid-root privileges could allow an attacker to read any file on the system by using a hand-crafted con-
figuration file. In fact, logfetch will attempt to remove its own suid-root setup if it detects that it has been installed suid-root.
ENVIRONMENT VARIABLES
DU Command used to collect information about the size of directories. By default, this is the command du -k. If the local du-command
on the client does not recognize the "-k" option, you should set the DU environment variable in the $BBHOME/etc/hobbitclient.cfg
file to a command that does report directory sizes in kilobytes.
FILES
$BBHOME/tmp/logfetch.cfg
$BBHOME/tmp/logfetch.status
SEE ALSO xymon(7), hobbit-clients.cfg(5)Xymon Version 4.2.3: 4 Feb 2009 LOGFETCH(1)