I recently started as an intern and my manager wanted to see how well I would handle Korn Bourne shell scripting without any prior experience, I have prior programming experience but I keep running into syntax errors with AWK. Please take a look at my simple code and tell me what stupid mistake... (6 Replies)
All,
Does it matter what perl verios your running when you get syntax errors?
on version 5.6.1 the code works fine, but on 5.8.0 the code gets errors?
#!/usr/bin/perl
#use strict;
#use warnings;
my $mess = 'messages';
my $mess1 = 'messages.1';
my $mess2 = 'messages.2';
my... (13 Replies)
Hi,
I am a newbie to PERL and working on a script. When running it I get a lot of compilation errors.
The actual command in the program (which is within a case structure) is given below
# This gives the actual count of inquires from a log file (It works fine when I type this on the... (2 Replies)
I want to delete archivelog files that has been archived and applied from primary database
to standby database. This piece of script is working in Linux server. However, I copy it to
Unix server with tiny modification. It won't work and generate the error message. I have checked
code carefullt... (8 Replies)
I have directory /test/logs which has multiple logs:
audit.log
audit.log.1
audit.log.2
audit.log.3
audit.log.4
audit.log.5
audit.log is current log file and audit.log.X are archive log files. I need to search within these log files and count word "error-5" logged within last 6 months... (4 Replies)
Original script written on CentOS 6.3 with GNU bash 4.1.2
Destination system is Solaris 9 with GNU bash 2.05 (not changeable by me)
I have a script written on the linux side but now we need to provide a version to another site that "doesn't like linux". I've been going through changing the ] or... (13 Replies)
Hello,
I have been working on Awk/sed one liner which counts the number of occurrences of '|' in pipe separated lines of file and delete the line from files if count exceeds "17".
i.e need to get records having exact 17 pipe separated fields(no more or less)
currently i have below :
awk... (1 Reply)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
This script will analyse the channels.txt e registrations.txt and it will allow to mage the channels and the... (9 Replies)
I believe there are couple of syntax issues in my script, couldn't find them :(
can someone help me with fixing it to make it work.
cd /abcde/
#get the latest filename excluding subdirs
filename=`ls -ltr | grep ^- | tail -1 | awk '{print $8}'`
#get system date and file timestamp and... (3 Replies)
Discussion started by: simpltyansh
3 Replies
LEARN ABOUT SUSE
error_at_line
ERROR(3) Linux Programmer's Manual ERROR(3)NAME
error, error_at_line, error_message_count, error_on_per_line, error_print_progname - glibc error reporting functions
SYNOPSIS
#include <error.h>
void error(int status, int errnum, const char *format, ...);
void error_at_line(int status, int errnum, const char *filename,
unsigned int linenum, const char *format, ...);
extern unsigned int error_message_count;
extern int error_one_per_line;
extern void (* error_print_progname) (void);
DESCRIPTION
error() is a general error reporting function. It flushes stdout, and then outputs to stderr the program name, a colon and a space, the
message specified by the printf(3)-style format string format, and, if errnum is nonzero, a second colon and a space followed by the string
given by perror(errnum). Any arguments required for format should follow format in the argument list. The output is terminated by a new-
line character.
The program name printed by error() is the value of the global variable program_invocation_name(3). program_invocation_name initially has
the same value as main()'s argv[0]. The value of this variable can be modified to change the output of error().
If status has a nonzero value, then error() calls exit(3) to terminate the program using the given value as the exit status.
The error_at_line() function is exactly the same as error(), except for the addition of the arguments filename and linenum. The output
produced is as for error(), except that after the program name are written: a colon, the value of filename, a colon, and the value of
linenum. The preprocessor values __LINE__ and __FILE__ may be useful when calling error_at_line(), but other values can also be used. For
example, these arguments could refer to a location in an input file.
If the global variable error_one_per_line is set nonzero, a sequence of error_at_line() calls with the same value of filename and linenum
will result in only one message (the first) being output.
The global variable error_message_count counts the number of messages that have been output by error() and error_at_line().
If the global variable error_print_progname is assigned the address of a function (i.e., is not NULL), then that function is called instead
of prefixing the message with the program name and colon. The function should print a suitable string to stderr.
CONFORMING TO
These functions and variables are GNU extensions, and should not be used in programs intended to be portable.
SEE ALSO err(3), errno(3), exit(3), perror(3), program_invocation_name(3), strerror(3)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 2006-04-25 ERROR(3)