Hi all,
I have some script that creates a temp csv file. What I need to do is do some search and replace and modify the file from my shell script. I know the commands to open the file and then apply the reg ex but wasnt sure how I could do this from a script and modify the file?
Any help... (2 Replies)
Hi,
I have a unix shell script that is outputting results from an SQL query to a *.csv file, using utl_file.put_line. The resulting file is then sent out via e-mail as a mail attachment.
The issue I have is that when the mailed attachment is opened in Excel the first column is shown as... (1 Reply)
I have a file in multiple directory which has some records in the following format
File: a/latest.txt , b/latest.txt, c/latest.txt ->
Name=Jhon
Age=27
Gender=M
Street=LA Road
Occupation=Service
I want to generate a csv file from the above file as follows
File: output.csv ->
... (9 Replies)
Friends...This is the first time i am trying the report generation using shell script... any suggestions are welcome.
Is there a way to set the font size & color when i am exporting the data from unix shell script as a CSV file ?
The following sample data is saved as a .csv file in the... (2 Replies)
Hello !
I am very aware that this is not the first time this question is asked here, because I have already read a lot of previous answers, but none of them worked, so...
As said in the title, I want to read a csv file with a bash script.
Here is a sample of the file:
... (4 Replies)
Discussion started by: Grhyll
4 Replies
6. Post Here to Contact Site Administrators and Moderators
Hi All,
There are list of 4-5 .csv files which has 12 columns.In some cases one of the record is split into 2 records. What needs to be done is this split record has to be auto corrected and placed in the csv file.
Eg:
Let us consider sample.csv file and in normal conditions the file... (1 Reply)
I have input data looks like this which is a part of a csv file
7,1265,76548,"0102:04"
8,1266,76545,"0112:04"
I need to make the output data should look like this and the output data will be part of text file:
7|1265000 |7654899 |A|
8|12660000 |76545999 |B|
The logic behind the... (6 Replies)
Hello Unix Shell Script Experts,
I have a script that would mask the columns in .csv file or .txt file.
First the script will untar the .zip files from Archive folder and processes into work folder and finally pushes the masked .csv files into Feed folder.
Two parameters are passed
... (5 Replies)
I have files in a Linux directory . Some of the file is listed below
-rw-rw-r--. 1 roots roots 0 Dec 23 02:17 zzz_123_00000_A_1.csv
-rw-rw-r--. 1 roots roots 0 Dec 23 02:18 zzz_121_00000_A_2.csv
-rw-rw-r--. 1 roots roots 0 Dec 23 02:18 zzz_124_00000_A_3.csv
drwxrwxr-x. 2 roots roots 6 Dec 23... (4 Replies)
If a command is not found, e.g. nawk, this is how I fix the problem
] && NAWK=/usr/bin/gawk
] && NAWK=/usr/bin/nawk
] && NAWK=/usr/bin/awkI use $NAWK an the set the appropriate value based on the system it runs.
How can I implement a similar fix for a command found but illegal argument.... (6 Replies)
Discussion started by: mohtashims
6 Replies
LEARN ABOUT REDHAT
inncheck
INNCHECK(8) System Manager's Manual INNCHECK(8)NAME
inncheck - check inn configuration and database files.
SYNOPSIS
inncheck [ -a ] [ -v ] [ -pedantic ] [ -f ] [ -perm ] [ -noperm ] [ file=value | file ]
DESCRIPTION
Inncheck examines various configuration files and databases and verifies things about them. Things verified depend on the file being
checked, but generally are things like permissions, ownership, syntax errors in config files etc.
Inncheck does not make changes to any files -- it just reports what it thinks may be wrong, and it is up to the operator to fix the prob-
lem.
The set of files checked may be restricted by using file or file=value arguments. For example, putting incoming.conf causes only the incom-
ing.conf(5) file to be checked. Using incoming.conf=/tmp/incoming.conf on the command line will cause inncheck to only verify the incom-
ing.conf file, and it will perform the checks on the file /tmp/incoming.conf file instead of the default one.
Valid values for file are:
active
control.ctl
expire.ctl
incoming.conf
inn.conf
moderators
newsfeeds
overview.fmt
nntpsend.ctl
passwd.nntp
OPTIONS -a If any ``file'' value or ``file=value'' pairs (see below) are given, then normally only the files they refer to are checked. Use the
``-a'' flag to specify that all files should be checked regardless. In this case the form file=value will be the more useful.
-v Use the ``-v'' option to get more verbose output.
-pedantic
Use the ``-pedantic'' option to get reports on things that are not necessarily wrong, but may indicate a bad configuration -- such
as inn.conf(5) missing a key.
-f Use the ``-f'' flag to have inncheck print the appropriate chown/chgrp/chmod command necessary to fix a problem that it reports.
Any other output lines will be prefixed with a ``#'' character to make the output be valid input for a shell. Note that the
``-perm'' flag must be used as well when using this flag.
-perm Inncheck checks all files for permission problems. If the ``-perm'' flag is used, then only the files specified by the file or
file=value command line arguments will be checked for problems other than permission problems.
-noperm
To avoid doing any checking of file permissions or ownership, use the ``-noperm'' option.
EXAMPLES
To have inncheck check all files for syntax and permission problems simply:
inncheck
To have inncheck check all files for permission problems and to verify the syntax of the active and incoming.conf files do:
inncheck -perm active incoming.conf
To have inncheck check the test newsfeeds file in /var/tmp/newsfeeds.testing, do:
inncheck newsfeeds=/var/tmp/newsfeeds.testing
To have inncheck check all the files as it normally does, but to specify a different location for the newsfeeds file, so:
inncheck -a newsfeeds=/var/tmp/newsfeeds.testing
BUGS
If the ``-f'' and ``-perm'' options are used together, along with ``-a'' or some ``file'' or ``file=value'' arguments that refer to a file
with a syntax problem, then the output will no longer be valid input for a shell.
HISTORY
Written by Brendan Kehoe <brendan@cygnus.com> and Rich Salz <rsalz@uunet.uu.net> This is revision 1.5, dated 1998/10/30.
SEE ALSO active(5), expire.ctl(5), history(5), incoming.conf(5), inn.conf(5), newsfeeds(5)INNCHECK(8)