Hi
I have a problem in installing solaris 9 in a ULTRA Enterprise 2 machine.
The cdrom does not keep the cd in. When I put the installtion cd 1 and close the tray, I can see the led blinks three times and then the tray comes out. I borrowed a set of installtion cd s from one of my friends (they... (3 Replies)
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Hi,
I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Hi Team,
I have a file named as follows: aaa.tar.gz
Now I need to verify if the untar fails, then the script has to send a mail. In order to check this condition, I need a tar.gz file which is unable to untar it. Can anyone help me to create a file which I will be able to unzip successfully... (2 Replies)
Discussion started by: kmanivan82
2 Replies
6. Forum Support Area for Unregistered Users & Account Problems
After inputted all required fields in registration page, the below message is shown and cannot go on.
A required field called Custom Date & Time Formats is missing or has an invalid value. (2 Replies)
Discussion started by: Unregistered
2 Replies
LEARN ABOUT NETBSD
mkstr
MKSTR(1) BSD General Commands Manual MKSTR(1)NAME
mkstr -- create an error message file by massaging C source
SYNOPSIS
mkstr [-] messagefile prefix file ...
DESCRIPTION
mkstr creates files containing error messages extracted from C source, and restructures the same C source, to use the created error message
file. The intent of mkstr was to reduce the size of large programs and reduce swapping (see BUGS section below).
mkstr processes each of the specified files, placing a restructured version of the input in a file whose name consists of the specified
prefix and the original name. A typical usage of mkstr is
mkstr pistrings xx *.c
This command causes all the error messages from the C source files in the current directory to be placed in the file pistrings and restruc-
tured copies of the sources to be placed in files whose names are prefixed with xx.
Options:
- Error messages are placed at the end of the specified message file for recompiling part of a large mkstr ed program.
mkstr finds error messages in the source by searching for the string `error("' in the input stream. Each time it occurs, the C string start-
ing at the '"' is stored in the message file followed by a null character and a new-line character; The new source is restructured with
lseek(2) pointers into the error message file for retrieval.
char efilname = "/usr/lib/pi_strings";
int efil = -1;
error(a1, a2, a3, a4)
{
char buf[256];
if (efil < 0) {
efil = open(efilname, 0);
if (efil < 0) {
oops:
perror(efilname);
exit 1 ;
}
}
if (lseek(efil, a1, 0) < 0 || read(efil, buf, 256) <= 0)
goto oops;
printf(buf, a2, a3, a4);
}
SEE ALSO xstr(1), lseek(2)HISTORY
mkstr appeared in 3.0BSD.
BUGS
mkstr was intended for the limited architecture of the PDP-11 family. Very few programs actually use it. It is not an efficient method, the
error messages should be stored in the program text.
BSD June 6, 1993 BSD