Hi Expert,
I have some confusing to generate report from the log file as shown below:
filename :test1.log
start_time date end_time number code
P 000029.621 20070823 000029 12134567890 111111111111 00 0 000 003... (4 Replies)
Hi Team,
I need a suggestion/comments for my below requirement.
I have a procedure which performs some DDL operations & loads data into a Oracle table. This status contains Audit data.
What i wanted to do is, once the procedure is completed (daily), shell script should retrive the data from the... (4 Replies)
Hi
Please help me to resolve the below query.
My shell script has generated a file output.file like below
********************************
DROP TABLE GPS_CONTACT_DETAILS
DB20000I The SQL command completed successfully.
CREATE TABLE GPS_CONTACT_DETAILS ( CONTACT_ID ... (8 Replies)
Hi
Is there a way to re-generate AIX error report after clearing it? I mean if I did errclear 0, Does the error log get erased? Is there a command that will get entries back in errpt?
I hope that made sense. (5 Replies)
Hi All,
I need to develop a shell script which does sanity check of a data file, as below.
1. For DATE columns, it should check if date is given in proper format or not? For example, if format of date is expected as DD-MON-YYYY HH24:MI:SS and we received the date in formation like DDMMYYYY HH24,... (1 Reply)
Hello Gurus
Is anyone aware of a script/utility that can be used to generate a report from a combined "sudoers" file for more than 100 servers in one go please?
Basic query: Which particular user or an user group can execute root equivalent commands or has the ability for e.g. to do a... (1 Reply)
Hi All,
Script to meet my requirement might be simpler for UINIX experts.. :)
I need to generate an summary report in .txt file using shell script
I have Reject directory in Unix server which contains all reject files for three diff categories- Presentation, Chapter and Scene
Following... (3 Replies)
I have 3 user in my linux machine let's say a,b,c .By Using last command I am able to identify list of last logged in user and by w command who is logged in and what they are doing and by history command all command used by particular user all will be shown.
Now I want to write shell script... (1 Reply)
There can be thousand of .ksh in a specific directory where sql files are called from ksh.
Requirement is to loop through all the files content and generate a report like below:
Jobname Type type sqlname
gemd1970 sql daily tran01
gemw1971 sql weekly ... (6 Replies)
Hi ,
In a directory list of ddl files are stored in the given format above. Above is the sample ddl file. The ddl file name is same as that of table name ie email_notifications.ddl
I want to generate below report using awk utility reading all the ddl files stored in /ddl path
Desired output:... (1 Reply)
Discussion started by: vedanta
1 Replies
LEARN ABOUT DEBIAN
apsfilter-bug
APSFILTER-BUG(1) BSD General Commands Manual APSFILTER-BUG(1)NAME
apsfilter-bug -- create a half-automatic bug report for apsfilter
SYNOPSIS
apsfilter-bug
OPTIONS
none
DESCRIPTION
With the apsfilter-bug script you can automatically create a bug report for apsfilter(1). A template report file is created which you can
edit with your favourite editor ( emacs(1) by default, or whatever is entered in the environment variable EDITOR ).
You will see a couple of lines starting with '#'; these lines will be removed before the report is sent. So if you want to use the '#' char-
acter at the beginning of a line, just indent it with a space.
A very important piece of the bug report is the debugging log created by aps2file(1), probably with a command like
aps2file -D -o /dev/null [-P...] [-Z...] [input] 2> log.txt
Unless you don't even have a chance to create a debugging log, it is crucial for serious bug hunting.
After you have filled in as much (useful) information as possible, you must save the file under its original name, then exit your editor.
If you invoked apsfilter-bug by accident, or if you need some additional system information to include into the bug report, just exit your
editor without saving the file.
NOTES
In addition to the stuff you've edited, some more information is appended to the bug report automatically:
apsfilter version 7.2.6-stable
ghostscript version (from 'gs --version')
system id (from 'uname -a')
configure options --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-awk=/usr/bin/awk --with-sendmail=/usr/sbin/sendmail
shell executable /bin/bash
awk executable /usr/bin/awk
sendmail executable /usr/sbin/sendmail
FILES
/usr/bin/aps2file script to create debugging output
SEE ALSO apsfilter(1), aps2file(1)BUGS
See apsfilter software center - http://www.apsfilter.org/ - for new versions, bugfixes and known bugs.
Please use the new tool apsfilter-bug(1) to release bug- or problem reports. It automatically presents you a form in an editor window which
asks you some standard questions. If you save and quit the editor session, then this report is sent automatically via e-mail to the proper
apsfilter mailinglist.
If apsfilter fails to print something or prints it in a way you wouldn't expect and you want to report an apsfilter error then please save
the debugging output of one print session using the new aps2file(1) utility by typing aps2file -D -Z options file > /dev/null 2> file.debug
and including the debugging output in the file file.debug into the edit session of the apsfilter-bug utility, so that it is included into the
mail to the apsfilter mailinglist.
Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works.
Under C-shell (/bin/csh) or tcsh it would't work. If you don't know, then simply make sure you use the Bournce shell by typing /bin/sh or
bash, then you should have no problems with redirection of stdout and stderr (> /dev/null 2> file.debug).
DOCUMENTATION
See official apsfilter homepage
http://www.apsfilter.org/handbook.html Apsfilter Handbook including the Frequently Asked Questions (FAQ)
USER FORUM
Please send questions to the official apsfilter help channel apsfilter-help@apsfilter.org. The above section BUGS and the file
HOWTO-BUGREPORTS tells you how to report bugs. If you want to know how to troubleshoot your apsfilter installation, please read the manpage
aps2file(1) and apsfilter-bug(1) as well as the Apsfilter Handbook carefully.
HISTORY
The apsfilter-bug manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.
BSD Dec 26, 2001 BSD