grep error message Post: 76927

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

error message

Hi All, occasionally my server gives this error messages "NOTICE:HTFS Out of inodes on HTFS dev hd (1/42)" why ?? Alice.

2. UNIX for Dummies Questions & Answers

Error Message

What does this means? - ERROR OPENING FILE - KEY LENGHT MISMATCH

3. Shell Programming and Scripting

Grep/awk not getting the message correctly

I have a script which will take two file as the inputs and take the Value in file1 and search in file2 and give the output in Outputfile. #!/bin/sh #. ${HOME}/crossworlds/bin/CWSharedEnv.sh FILE1=$1 FILE2=$2 for Var in $(cat $FILE1);do echo $Var grep -i "$Var" $FILE2 done > Outputfile I...

4. Shell Programming and Scripting

grep'ing a file until a certain message appears

Hello, I'm writing a script that will automate the launch of some services on my AIX machine. However, some services are dependent on the successful startup of others. When I start these services manually, I usually just check a log file until I see a message that confirms a successful...

5. UNIX for Advanced & Expert Users

Is there a better way to grep until end of error message?

My file creates an output log after which includes a few sql queries. I segregate them into warnings and errors and then get a total count. The errors' and warnings' lines always start with SQL{4} followed by the details of the error. This is what im doing as o now... errors=`grep -A 1 -E...

6. Shell Programming and Scripting

a better way to grep until end of error message, although most seem to be 1 or 2 line

7. Shell Programming and Scripting

How to grep for message and if found display filename?

Hi i'm new to the forum and was hoping someone could help me with the following query. I do alot of testing and have hundreds of log files output. I have a script (someone else wrote) which finds all the passed and failed logs and puts a number in a column onto a webpage: e.g: Pass ...

8. Shell Programming and Scripting

script to grep outofmemory message in logs

I have prepare script to grep for outofmemory messages in the logs. I need help in modifying script. I have implemented small logic. The outofmemory messages form six logs will store in variables. var1=`grep -i outofmemory $tomcat1logs | sed -n '$p'| sed -n -e "s/.*$outofmemory$.*/\1/p"`...

9. Shell Programming and Scripting

Not able to grep a particular message in logfile.

Hi I am not able to grep a message in a log file - For ex - Notice < > "Server1" is in deploying state under "Stut" domain When i use gzcat logfile | grep -i " Notice < > "Server1" is in deploying state under "Stut" domain" It is not returning any value. Is it because of "Server1"...

10. Shell Programming and Scripting

Grep: Return a user message when no hits

I have ASCII files to parse that 48 hours old or more ; I can identify them like so find . -name "FILE*TXT" -mtime +1 -exec ls -ltas '{}' ';' Some files have a list of hardware errors (we test electronic components), some have none. If the file name has no errors, I still want to...

LEARN ABOUT SUSE

unpost_form

post(3FORM)															       post(3FORM)

NAME

       post - write or erase forms from associated subwindows

SYNOPSIS

       #include <form.h>
       int post_form(FORM *form);
       int unpost_form(FORM *form);

DESCRIPTION

       The  function  post_form  displays  a  form to its associated subwindow.  To trigger physical display of the subwindow, use refresh or some
       equivalent curses routine (the implicit doupdate triggered by an curses input request will do).

       The function unpost_form erases form from its associated subwindow.

RETURN VALUE

       These routines return one of the following:

       E_OK The routine succeeded.

       E_BAD_ARGUMENT
	    Routine detected an incorrect or out-of-range argument.

       E_BAD_STATE
	    Routine was called from an initialization or termination function.

       E_NOT_POSTED
	    The form has not been posted.

       E_NOT_CONNECTED
	    No items are connected to the form.

       E_NO_ROOM
	    Form is too large for its window.

       E_POSTED
	    The form has already been posted.

       E_SYSTEM_ERROR
	    System error occurred (see errno).

SEE ALSO

       ncurses(3NCURSES), form(3FORM).

NOTES

       The header file <form.h> automatically includes the header file <curses.h>.

PORTABILITY

       These routines emulate the System V forms library.  They were not supported on Version 7 or BSD versions.

AUTHORS

       Juergen Pfeifer.  Manual pages and adaptation for new curses by Eric S. Raymond.

																       post(3FORM)