10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error.
#! /bin/sh
errExit ()
{
errMsg=`cat... (1 Reply)
Discussion started by: sarathy_a35
1 Replies
2. Solaris
I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet.
... (2 Replies)
Discussion started by: christr
2 Replies
3. Shell Programming and Scripting
what is this error log = hda: irq timeout: error=0x00 and how to solve?
every day upon checking the logs i see this error.
hda: irq timeout: error=0x00
hda: irq timeout: error=0x00
hda: irq timeout: error=0x00
hda: irq timeout: error=0x00
hw_client: segfault at 0000000000000046 rip... (3 Replies)
Discussion started by: avtalan
3 Replies
4. UNIX for Dummies Questions & Answers
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies
5. UNIX for Advanced & Expert Users
Hi - I am getting the error
`Error reading response length from authentication socket'
when I ssh from my cluster to another cluster, and then back to my cluster. It doesn't seem to affect anything, but it's just annoying that it always pops up and tends to confuse new users of the cluster. I... (1 Reply)
Discussion started by: cpp6f
1 Replies
6. Solaris
Hi Guys.
This is part of my filesystem structure :
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 47G 5.2G 42G 12% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% ... (2 Replies)
Discussion started by: aggadtech08
2 Replies
7. AIX
--------------------------------------------------------------------------------
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies
8. UNIX for Advanced & Expert Users
I encounters a VSIFAX related error:
vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument
It started happening last night with a core dump. Then we can't start VSIFAX again.
I am runing VSI-FAX 4.2 on AIX box (0 Replies)
Discussion started by: b_jin
0 Replies
9. UNIX for Dummies Questions & Answers
hi there
i write one awk script file in shell programing
the code is related to dd/mm/yy to month, day year format
but i get an error
please can anybody help me out in this problem ??????
i give my code here including error
awk `
# date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies
10. UNIX for Dummies Questions & Answers
Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message.
Error: Internal system error: Unable to initialize standard output file
I'm guessing more info might be needed, so let me know.
Thanks (2 Replies)
Discussion started by: firkus
2 Replies
erl_lint(3erl) Erlang Module Definition erl_lint(3erl)
NAME
erl_lint - The Erlang Code Linter
DESCRIPTION
This module is used to check Erlang code for illegal syntax and other bugs. It also warns against coding practices which are not recom-
mended.
The errors detected include:
* redefined and undefined functions
* unbound and unsafe variables
* illegal record usage.
Warnings include:
* unused functions and imports
* unused variables
* variables imported into matches
* variables exported from if / case / receive
* variables shadowed in lambdas and list comprehensions.
Some of the warnings are optional, and can be turned on by giving the appropriate option, described below.
The functions in this module are invoked automatically by the Erlang compiler and there is no reason to invoke these functions separately
unless you have written your own Erlang compiler.
EXPORTS
module(AbsForms) -> {ok,Warnings} | {error,Errors,Warnings}
module(AbsForms, FileName) -> {ok,Warnings} | {error,Errors,Warnings}
module(AbsForms, FileName, CompileOptions) -> {ok,Warnings} | {error,Errors,Warnings}
Types AbsForms = [term()]
FileName = FileName2 = atom() | string()
Warnings = Errors = [{Filename2,[ErrorInfo]}]
ErrorInfo = see separate description below.
CompileOptions = [term()]
This function checks all the forms in a module for errors. It returns:
{ok,Warnings} :
There were no errors in the module.
{error,Errors,Warnings} :
There were errors in the module.
Since this module is of interest only to the maintainers of the compiler, and to avoid having the same description in two places to
avoid the usual maintenance nightmare, the elements of Options that control the warnings are only described in compile(3erl) .
The AbsForms of a module which comes from a file that is read through epp , the Erlang pre-processor, can come from many files. This
means that any references to errors must include the file name (see epp(3erl) , or parser erl_parse(3erl) ). The warnings and errors
returned have the following format:
[{FileName2,[ErrorInfo]}]
The errors and warnings are listed in the order in which they are encountered in the forms. This means that the errors from one file
may be split into different entries in the list of errors.
is_guard_test(Expr) -> bool()
Types Expr = term()
This function tests if Expr is a legal guard test. Expr is an Erlang term representing the abstract form for the expression.
erl_parse:parse_exprs(Tokens) can be used to generate a list of Expr .
format_error(ErrorDescriptor) -> Chars
Types ErrorDescriptor = errordesc()
Chars = [char() | Chars]
Takes an ErrorDescriptor and returns a string which describes the error or warning. This function is usually called implicitly when
processing an ErrorInfo structure (see below).
ERROR INFORMATION
The ErrorInfo mentioned above is the standard ErrorInfo structure which is returned from all IO modules. It has the following format:
{ErrorLine, Module, ErrorDescriptor}
A string which describes the error is obtained with the following call:
Module:format_error(ErrorDescriptor)
SEE ALSO
erl_parse(3erl) , epp(3erl)
Ericsson AB stdlib 1.17.3 erl_lint(3erl)