12-27-2007
Thank you siva and rtm
You guys got it man. It was that stupid space. Duh.. I cannot believe i made that mistake.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello:
I'm having the following problem when I try to log in to our Tru64 system, from any machine using root or any other user.
After entering the passowrd I get the following message:
and not being directed to the shell console.
I think it has something to do with the audit process... (2 Replies)
Discussion started by: aladdin
2 Replies
2. Solaris
Dear all
I am facing a problem that I cannot able to login through 192.168.11.6. I even unplumb it and then plumb it again also, but still facing a problem. Could anyone tell me that what is the meaning of "inet 192.168.11.6 --> 192.168.11.6". I even restart the server two time also ,but still... (7 Replies)
Discussion started by: girish.batra
7 Replies
3. Shell Programming and Scripting
Hi all..
The following set of statements is used in a shell script to ftp a file to a remote machine
I want to redirect the ftp messages thrown by the first ftp statement to a log file. As you can see there is a logic downstream to decide if the ftp was a success or not. But i am not... (5 Replies)
Discussion started by: hareeshkumaru
5 Replies
4. Shell Programming and Scripting
If a log file is in the following format
28-Jul-10 ::: Log message
28-Jul-10 ::: Log message
29-Jul-10 ::: Log message
30-Jul-10 ::: Log message
31-Jul-10 ::: Log message
31-Jul-10 ::: Log message
1-Aug-10 ::: Log message
1-Aug-10 ::: Log message
2-Aug-10 ::: Log message
2-Aug-10 :::... (3 Replies)
Discussion started by: vikram3.r
3 Replies
5. Shell Programming and Scripting
Hi,
I have a problem with my logfile. I am redirecting my output to log file and when iam viewing as text doc it is looking with some nonsense characters...please do help me on this .thank you.
here is my logfile which it is showing different behaviour:
spawn
spawn minicom
Welcome... (6 Replies)
Discussion started by: vanid
6 Replies
6. Shell Programming and Scripting
Hi
I have a requirement to write a script to capture all errors in a Logfile and send the file in email.
If there is any error occurred the subject of email will be ERROR , If there are no error occurred the subject of email will be SUCCESS.
So I created a Log file and put the Appropriate... (2 Replies)
Discussion started by: dgmm
2 Replies
7. Shell Programming and Scripting
Hi,
I have written a bash shell script. In order to create a log file when I run the script, as well as print the output to the terminal, I call it in the following manner:
my_shell_script 2>&1 | tee my_log_fileThis seems to work well. However, I have put some statements in the script to... (2 Replies)
Discussion started by: msb65
2 Replies
8. Shell Programming and Scripting
Hi,
I am in trouble ... again :wall:
I formating a log file as .txt from Unix (solaris 9) and then I compress it with gzip and I use uuencode and send it in an email.
gzip -c ${fic_report} | uuencode Report_File.gz > ${attachment_file}
my problem is when I received the mail with the... (6 Replies)
Discussion started by: Aswex
6 Replies
9. Solaris
Hi,
I have a log file that i'd like to monitor for a string. Now the log file rolls over everytime the server is restarted, so i'm doing a reverse list and then reading the latest log file.
So for the code, the log file is 'test1.txt'.
I check for the string and pipe to black hole (>... (2 Replies)
Discussion started by: horhif
2 Replies
10. Shell Programming and Scripting
I need to create shell script (check system ) to display the output to the console and write these output to a log file at the same time.
My shell script is like that
Main() {
....
....
}
MainIt takes about 30s to display all the output to the console.
Then I put this command to the... (4 Replies)
Discussion started by: bobochacha29
4 Replies
LEARN ABOUT SUSE
assert_perror
ASSERT_PERROR(3) Linux Programmer's Manual ASSERT_PERROR(3)
NAME
assert_perror - test errnum and abort
SYNOPSIS
#define _GNU_SOURCE
#include <assert.h>
void assert_perror(int errnum);
DESCRIPTION
If the macro NDEBUG was defined at the moment <assert.h> was last included, the macro assert_perror() generates no code, and hence does
nothing at all. Otherwise, the macro assert_perror() prints an error message to standard error and terminates the program by calling
abort(3) if errnum is nonzero. The message contains the filename, function name and line number of the macro call, and the output of str-
error(errnum).
RETURN VALUE
No value is returned.
CONFORMING TO
This is a GNU extension.
BUGS
The purpose of the assert macros is to help the programmer find bugs in his program, things that cannot happen unless there was a coding
mistake. However, with system or library calls the situation is rather different, and error returns can happen, and will happen, and
should be tested for. Not by an assert, where the test goes away when NDEBUG is defined, but by proper error handling code. Never use
this macro.
SEE ALSO
abort(3), assert(3), exit(3), strerror(3), feature_test_macros(7)
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
GNU
2002-08-25 ASSERT_PERROR(3)