Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Understanding the output command Post 302386802 by Ariean on Wednesday 13th of January 2010 03:22:36 PM
Old 01-13-2010
I am missing something what do u mean by standard error? i understand standard output is the output printed on screen when i execute the script. But i didn't understand "2>&1" part, whats happening over there?

Thanks,
Ariean
 

10 More Discussions You Might Find Interesting

1. OS X (Apple)

Ifconfig output - help understanding flags 'Smart, Simplex', etc

Hi - Trying to understand a few things from an ifconfig -a output - can't seem to find info anywhere on the net. Specifically - looking to understand the following: Flags=8863 Smart Running (is this the same as UP) Simplex inet6 supported media: autoselect - does that imply the... (1 Reply)
Discussion started by: littlefrog
1 Replies

2. UNIX for Dummies Questions & Answers

Help Understanding Output and question about /dev/

Hi, I am having some problems understanding the info from the following output: Disk /dev/sda: 17849 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sda1 *... (5 Replies)
Discussion started by: mojoman
5 Replies

3. Shell Programming and Scripting

understanding mv command

hi i was moving a file from one directory to another with the following cmmand mv /home/hsghh/dfd/parent/file.txt . while doing so i i accidently mv /home/hsghh/dfd/dfd . although i gave ctrl c and terminate the move command some of the file are missing in the parent directory and... (1 Reply)
Discussion started by: saravanan71184
1 Replies

4. Shell Programming and Scripting

Understanding the output of TOP

ok, so I have a script im running on a linux box that uses "egrep" a lot. now, when i run this script, i check the TOP to see how much system resource it is using. the "top" command gives the following output: last pid: 25384; load avg: 1.06, 1.04, 0.76; up 351+06:30:24 ... (0 Replies)
Discussion started by: SkySmart
0 Replies

5. Solaris

Understanding 'du' command

Hi I have a questions related 2 commands : 'du' and 'ls'. Why is the difference between output of 'du' and 'ls' cmd's ? Command 'du' : ------------------ jakubn@server1 /home/jakubn $ du -s * 4 engine.ksh 1331 scripts 'du -s *' ---> shows block count size on disk (512 Bytes... (5 Replies)
Discussion started by: presul
5 Replies

6. UNIX for Dummies Questions & Answers

Understanding nm command output

After running nm command on any object file from out put can we get to know that wheather a symbol is a call to a function or definition of function ? I am searching a class and function definitions inside many .so files. I have 3 files which contain the symbol but I don't know wheather they... (2 Replies)
Discussion started by: yatrik007
2 Replies

7. Shell Programming and Scripting

Understanding the output of fwtmp

Hi all, First time post, so please be gentle. :) I'm writing a Solaris 10 ksh script to retrieve details of logins and logouts using specific user names. The details I want are quite basic - the username, the computer logged in from, and the date and time the user logged in and logged off.... (6 Replies)
Discussion started by: confusedAdmin
6 Replies

8. Red Hat

Command understanding the output file destination in case of standard output!!!!!

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

9. UNIX for Advanced & Expert Users

Understanding output of "last" command

Hello, Been looking through Google, and I don't see a direct answer to this: # last ... abcd pts/1 srever02 Mon Feb 23 07:56 - 07:56 (00:00) abcd sshd server02 Mon Feb 23 07:56 - 07:56 (00:00) klmn sshd ... (2 Replies)
Discussion started by: kitykitykity
2 Replies

10. Shell Programming and Scripting

Insert title as output of command to appended file if no output from command

I am using UNIX to create a script on our system. I have setup my commands to append their output to an outage file. However, some of the commands return no output and so I would like something to take their place. What I need The following command is placed at the prompt: TICLI... (4 Replies)
Discussion started by: jbrass
4 Replies
fitscheck(1)							   PyFITS 3.0.7 						      fitscheck(1)

NAME
fitscheck - script to detect and fix FITS standards violations SYNOPSIS
fitscheck [OPTION]... [FILE]... DESCRIPTION
fitscheck is a command line script based on pyfits for verifying and updating the CHECKSUM and DATASUM keywords of FITS files. itscheck can also detect and often fix other FITS standards violations. fitscheck facilitates re-writing the non-standard checksums originally gen- erated by pyfits with standard checksums which will interoperate with cfitsio. fitscheck will refuse to write new checksums if the checksum keywords are missing or their values are bad. Use --force to write new check- sums regardless of whether or not they currently exist or pass. Use --ignore-missing to tolerate missing checksum keywords without com- ment. OPTIONS
-h, --help Display terse usage information (help). -k [standard | nonstandard | either | none], --checksum=[standard | nonstandard | either | none] Choose FITS checksum mode or none. Defaults to standard. -w, --write Write out file checksums and/or FITS compliance fixes. -f, --force Do file update even if original checksum was bad. -c, --compliance Do FITS compliance checking, fix if possible. -i, --ignore-missing Ignore missing checksums. -v, --verbose Generate extra output. EXAMPLES
% fitscheck --checksum either --write *.fits Verify and update checksums, tolerating non-standard checksums, updating to standard checksum. % fitscheck --write --force *.fits Write new checksums, even if existing checksums are bad or missing. % fitscheck --compliance *.fits Verify standard checksums and FITS compliance without changing the files. % fitscheck --checksum nonstandard *.fits Verify original nonstandard checksums only. % fitscheck --checksum none --compliance --write *.fits Only check and fix compliance problems, ignoring checksums. % fitscheck *.fits Verify standard interoperable checksums. % fitscheck --checksum none --write *.fits Delete checksum keywords. fitscheck June 2012 fitscheck(1)
All times are GMT -4. The time now is 03:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy