10 More Discussions You Might Find Interesting
1. Red Hat
I ran the following command.
cat abc.c > abc.c
I got message the following message from command cat:
cat: abc.c : input file is same as the output file
How the command came to know of the destination file name as the command is sending output to standard file. (3 Replies)
Discussion started by: ravisingh
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am facing issue while using scp. Source & target machines are Linux & HP-UX respectively.
On target machine, if I fire the following command, I get error:
Now if I try scp on another file, which is on the same source machine, it works fine.
All directories and subdirectories... (2 Replies)
Discussion started by: Technext
2 Replies
3. SCO
Hello...
i got an error in my SCO OpenServer 6. the error is:
msgcnt 1 vxfs: mesg 016: vx_ilisterr - / file system error reading inode 373
Can anyone help me? (1 Reply)
Discussion started by: AndryMB
1 Replies
4. UNIX for Dummies Questions & Answers
Hey, I'm completely new at this and I was wondering if there is a way that I would be able to redirect the log files in a directories standard output and standard error into and excel spreadsheet in anyway?
Please remember don't use too advanced of terminology as I just started using shell... (6 Replies)
Discussion started by: killaram
6 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I want to check a particular word is in standard error output or not. Can I acheive it in single command?
For example,
Delete file_name 2>error.log
cat error.log
Output:
XXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXX
Successfully deleted
XXXXXXXXXXXXXXXXX
where delete is... (2 Replies)
Discussion started by: poova
2 Replies
6. Shell Programming and Scripting
I have a weird situation in which the binary dumps core and gives bus error. But before dumping the core and throwing the buss error, it gives some output.
unfortunately I can't grep the output before core dump
db2bfd -b test.bnd
maxSect 15
Bus Error (core dumped)
But if I do ... (4 Replies)
Discussion started by: rakeshou
4 Replies
7. 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
8. Shell Programming and Scripting
Hi there
how can i get the result of a command to not give me its error. For example, on certain systems the 'zfs' command below is not available, but this is fine becaues I am testing against $? so i dont want to see the message " command not found" Ive tried outputting to /dev/null 2>&1 to no... (5 Replies)
Discussion started by: hcclnoodles
5 Replies
9. Shell Programming and Scripting
I'm writing a script using file descriptor 2 (std error) to send an email only if the command fails or errors out but the script always emails me irrepective of whether it fails or not. It will not email the /tmp/check.error file output if doesn't error out just the mail with the subject "Cannot... (3 Replies)
Discussion started by: barkath
3 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I am new in shell scripting.
Can anyone point out what wrong of below script.
If I want the error output to "sqlerror.log"
and database pool data output to "bulk_main.dat".
Right now, the below script, if successful execute, the data will output to
bulk_main.dat && sqlerror.log both... (7 Replies)
Discussion started by: epall
7 Replies
isl(1M) isl(1M)
NAME
isl - initial system loader
DESCRIPTION
implements the operating system independent portion of the bootstrap process. It is loaded and executed after self-test and initialization
have completed successfully.
The processor contains special purpose memory for maintaining critical configuration related parameters (e.g. Primary Boot, Alternate Boot,
and Console Paths). Two forms of memory are supported: Stable Storage and Non-Volatile Memory (NVM).
Typically, when control is transferred to an sequence takes place. An sequence allows a complete bootstrap operation to occur with no
intervention from an operator. executes commands from the file in a script-like fashion. is enabled by a flag in Stable Storage.
is a mechanism that automatically locates the boot and console devices. For further information, see pdc(1M).
During an sequence, displays its revision and the name of any utility it executes. However, if is disabled, after displays its revision,
it then prompts for input from the console device. Acceptable input is any command name or the name of any utility available on the sys-
tem. If a non-fatal error occurs or the executed utility returns, again prompts for input.
Commands
There are several commands available in although not all commads are supported on cellular systems . The following is a list with a short
description. Parameters may be entered on the command line following the command name. They must be separated by spaces. prompts for any
necessary parameters that are not entered on the command line.
Help - List commands and available utilities
List available utilities
Enable or disable the
autoboot sequence
Parameter - or
Enable or disable the
sequence
Parameter - or
Modify the Primary Boot Path
Parameter - Primary Boot Path in decimal
Modify the Alternate Boot Path
Parameter - Alternate Boot Path in decimal
Modify the Console Path
Parameter - Console Path in decimal
List contents of the
file
Display the Primary Boot, Alternate Boot, and Console Paths
Display the contents of one word of NVM in hexadecimal
Parameter - NVM address in decimal or standard hexadecimal notation
Display the contents of one word of Stable Storage in hexadecimal
Parameter - Stable Storage address in decimal or standard hexadecimal notation
DIAGNOSTICS
displays diagnostic information through error messages written on the console and display codes on the LED display.
For the display codes, are informative only. and indicate errors, some of which are fatal and cause the system to halt. Other errors
merely cause to display a message.
Non-fatal errors during an sequence cause the sequence to be aborted and to prompt for input. After non-fatal errors during an interactive
session, merely prompts for input.
Fatal errors cause the system to halt. The problem must be corrected and the system RESET to recover.
is executing.
is from the file.
Cannot find an
file. aborted.
No console found,
can only
Directory of utilities is too big,
reads only 2K bytes.
file is inconsistent.
aborted.
Utility file header inconsistent: SOM values invalid.
file input string exceeds 2048 characters.
aborted.
command or utility name exceeds 10 characters.
has transferred control to the utility.
Internal inconsistency: Volume label -
Internal inconsistency: Directory -
Error reading
file.
Error reading from console -
Error writing to console -
Not an command or utility.
Utility file header inconsistent: Invalid System ID.
Error reading utility file header.
Utility file header inconsistent: Bad magic number.
Utility would overlay
in memory.
Utility requires more memory than is configured.
Error reading utility into memory.
Incorrect checksum: Reading utility into memory.
Console needed -
Internal inconsistency: Boot device class -
Destination memory address of utility is invalid.
Utility file header inconsistent:
pdc_cache entry.
Internal inconsistency:
iodc_entry_init -
Internal inconsistency:
iodc_entry_init - console -
Internal inconsistency:
iodc_entry_init - boot device -
Utility file header inconsistent: Bad
aux_id.
Bad utility file type.
SEE ALSO
boot(1M), pdc(1M).
PA-RISC Systems Only isl(1M)