I'm trying to parse the variables out of a comma delimited expression, but i'm having trouble with script:
num_var=1
while
do
a=`echo "a=7, b=8, c=9" | awk '{print $num_var}' | cut -d= -f2`
b=`echo $a | cut -d, -f1`
echo $b
num_var=`expr $num_var + 1`... (5 Replies)
I need help with a problem that I have not been able to figure out.
I have a file that is about 650K lines. Records are seperated by
blank lines, fields seperated by new lines. I was trying to make
a report that would add up 2 fields and associate them with a CP.
example output would be... (11 Replies)
Hi,
I have a textfile with several lines like this:
text num: USER text (num) num num
I need all these stuff. Problem is, how to get these stuff after ":".
USER is a username and all chars are possible, even whitespace. So I cant use cut. Any ideas? (3 Replies)
Hi all,
I am having problems parsing the following file:
cat mylist
one,two,three
four
five,six
My goal is to get each number on a seperate line.
one
two
three
four
five
six
I tried this command:
sed -e 's/\,/^M/g' mylist (11 Replies)
Heya
Tooltip: Parsing (getopts) for -u successfully sets mode=umnt, but case umnt is not executed,
instead it either executes/show help or regular mount screen.
I had copy pasted the structure of a getopts 'structure' from Man Page for getopts (posix Section 1) - The UNIX and Linux Forums... (1 Reply)
Hello fellow unix geeks,
I am having a small dilemna trying to parse a log file I have. Below is a sample of what it will look like:
MY_TOKEN1(group) TOKEN(other)|SSID1
MY_TOKEN2(group, group2)|SSID2
What I need to do is only keep the MY_TOKEN pieces and where there are multiple... (7 Replies)
Discussion started by: dagamier
7 Replies
LEARN ABOUT SUNOS
chicken-bug
CHICKEN-BUG(1) General Commands Manual CHICKEN-BUG(1)NAME
chicken-bug - generates a bug report from user input
SYNOPSIS
chicken-bug [ filename | OPTION ... ]
OPTIONS -help Show usage information.
-to-stdout
Write bug report to standard output instead of writing it to a file.
- Read user input from standard input, even if files are given on the command line.
DESCRIPTION
chicken-bug generates a bug report file that collects user-input, optional files and system information obtained from the installed CHICKEN
executables and libraries. Non-option arguments given on the command line are inserted into the bug report. If no option is given, or if -
has been passed on the command line, then a description of the problem is read from standard input, until EOF (CTRL-D) or a line consisting
only of "." (period) is read.
The bug report will be written to a file in the current directory, which should be sent to CHICKEN maintainers as it contains various use-
ful bits of information that make it easier to classify the problem described.
Bug reports should be as detailed as possible. It is also very helpful to include code that reproduces the problem. The more detailed the
input and the more thorough the description is, the easier you make it for the CHICKEN developers to help you.
BUGS
Submit bug reports by e-mail to chicken-janitors@nongnu.org
AUTHOR
The CHICKEN Team.
SEE ALSO chicken(1)
19 Sep 2001 CHICKEN-BUG(1)