06-03-2002
Suggest you use Perl or some other language instead of trying to use the shell for open/read/write of files -
1. It would make more sense to you.
2. It would make you a better admin.
3. It would be easier as suggested by the responses to your inquiry.
The shell is not as powerful as OpenVMS in some aspects but more powerful than it in others. Using redirection, piping, and other tools will become easy after awhile. The only thing I found that I really missed was the search command which allowed you to search and see lines of code/data above/below the line you searched for.
7 More Discussions You Might Find Interesting
1. Solaris
Hi
want to know what file (descriptor+filename+socket) is being accessed by particular process on solaris.
Purpose : while running perf. test, needs to find where is the bottleneck.
We are providing concurrnet load for around 1 hr and needs to capture data related to file usage pattern... (1 Reply)
Discussion started by: raxitsheth
1 Replies
2. Red Hat
First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting.
First, this is what's running:
This is the error when jobs are run or the... (0 Replies)
Discussion started by: Katahdin
0 Replies
3. Shell Programming and Scripting
I am dealing will many thousand fairy small files.
I need to search them for various matches and depending on what I find, may need to search some files again for additional matches.
Generally speaking, is it better to write a txt file to an @array/@list and then work with it (multiple... (1 Reply)
Discussion started by: OldGaf
1 Replies
4. Shell Programming and Scripting
Hi All
I am a new in scripting language and I would like help for you guys
I would like to create a file named constant.h and search into all files *.m in specific directory for a reg-exp @"LBL_]+" exp: @"LBL_75847" , and write those matchs to constant.h if there are not written (no... (15 Replies)
Discussion started by: molwiko
15 Replies
5. Shell Programming and Scripting
Hello!
I am a real beginner in scripting, so I am struggling with a really easy task!
I want to write a script to concatenate several text files onto each other and generate a new file. I wanted the first argument to be the name of the new file, so:
./my_script.sh new_file file1.txt... (5 Replies)
Discussion started by: malajedala
5 Replies
6. UNIX for Beginners Questions & Answers
Hi Friends,
Every I try to open a vi window vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (1 Reply)
Discussion started by: sudiptabhaskar
1 Replies
7. Shell Programming and Scripting
Hi Friends,
Every I try to open a vi window, vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (3 Replies)
Discussion started by: sudiptabhaskar
3 Replies
ERR(3) BSD Library Functions Manual ERR(3)
NAME
err, verr, errx, verrx, warn, vwarn, warnx, vwarnx, -- formatted error messages
SYNOPSIS
#include <err.h>
void
err(int eval, const char *fmt, ...);
void
errx(int eval, const char *fmt, ...);
void
warn(const char *fmt, ...);
void
warnx(const char *fmt, ...);
#include <stdarg.h>
void
verr(int eval, const char *fmt, va_list args);
void
verrx(int eval, const char *fmt, va_list args);
void
vwarn(const char *fmt, va_list args);
void
vwarnx(const char *fmt, va_list args);
DESCRIPTION
The err() and warn() family of functions display a formatted error message on the standard error output. In all cases, the last component of
the program name, a colon character, and a space are output. If the fmt argument is not NULL, the printf(3) -like formatted error message is
output. The output is terminated by a newline character.
The err(), verr(), warn(), and vwarn() functions append an error message obtained from strerror(3) based on a code or the global variable
errno, preceded by another colon and space unless the fmt argument is NULL.
The err(), verr(), warn(), and vwarn() functions use the global variable errno to look up the error message.
The errx() and warnx() functions do not append an error message.
The err(), verr(), errx(), and verrx() functions do not return, but exit with the value of the argument eval.
EXAMPLES
Display the current errno information string and exit:
if ((p = malloc(size)) == NULL)
err(1, NULL);
if ((fd = open(file_name, O_RDONLY, 0)) == -1)
err(1, "%s", file_name);
Display an error message and exit:
if (tm.tm_hour < START_TIME)
errx(1, "too early, wait until %s", start_time_string);
Warn of an error:
if ((fd = open(raw_device, O_RDONLY, 0)) == -1)
warnx("%s: %s: trying the block device",
raw_device, strerror(errno));
if ((fd = open(block_device, O_RDONLY, 0)) == -1)
err(1, "%s", block_device);
SEE ALSO
exit(3), printf(3), perror(3), strerror(3)
HISTORY
The err() and warn() functions first appeared in 4.4BSD.
BSD
March 6, 1999 BSD