Sponsored Content
Top Forums Shell Programming and Scripting Print the one function's log to the screen Post 302926384 by yanglei_fage on Monday 24th of November 2014 12:04:01 AM
Old 11-24-2014
Print the one function's log to the screen

Code:
c()
{
     if something failed;then
    echo "failed"
    exit 1 
     fi
}

f()
{
functinona  #if something failed call "c"
functionb   #if something failed call "c"  
}

f > log 2>&1 #put the log to file not print on the screen


I want all the stdout/stdrr to the log file without print on the screen, but I want the function "c" 's output on the screen
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how to print screen in linux

Hi All, Perhaps a dumb question, but how do you do a "print screen" within the X-Window in linux. I'm running KDE, is there a utility I can use in that package that I'm not aware of. Or, is there a way to turn on the <alt><print-screen> function with the keyboard? Thanks in advance. VJ (2 Replies)
Discussion started by: vancouver_joe
2 Replies

2. UNIX for Advanced & Expert Users

How to print contents on the screen?

I have the following questions regrading Unix commands. 1. Could you provide the commands how to print the content of ".profile" and ".shrc" files on the screen using "more" and "piple" command? 2. How can i use the "head" and "tail" to display lines from 25 through 75... 3. How to search... (1 Reply)
Discussion started by: aadba
1 Replies

3. UNIX for Dummies Questions & Answers

How to print content on the screen

I have the following questions regrading Unix commands. 1. Could you provide the commands how to print the content of .profile and .shrc files on the screen using more and piple command? or a better way? 2. How can i use the head and tail to display lines from 25 through 75... or a better... (4 Replies)
Discussion started by: aadba
4 Replies

4. Shell Programming and Scripting

print to screen and to file using awk?!

Hello all!.. does anyone know the syntax to print to the screen and to a file? Im using something like AWK .... print header |tee -a invalid_csv_file ; END {..} ' invalid_csv_file="$invalid_csv_dir_file" but no joy? I get sh:... (2 Replies)
Discussion started by: satnamx
2 Replies

5. Shell Programming and Scripting

perl - print to a log file and screen

as the title suggests, i need to print a user message to a log file and the screen using perl. in unix i set up a function using 'tee' like so function Display_Message { echo "$*" | tee -ai $LOGFILE } the following command then obviously displays to the screen and prints to a log... (6 Replies)
Discussion started by: mjays
6 Replies

6. AIX

print screen

Hi all, Could you please tell me how to take a screenshot in aix (like Print Screen button in windows)? Thanks (7 Replies)
Discussion started by: prashantchavan
7 Replies

7. Shell Programming and Scripting

Print on the screen a table in ascii

Hi Is there some kind of generator in the internet which could help me to create a table where i will place some values. Trying to do this with echo cmd, but maybe you will suggest me some generator fo r this. thx. ---------- Post updated at 10:59 AM ---------- Previous update was at... (2 Replies)
Discussion started by: presul
2 Replies

8. Shell Programming and Scripting

Print from screen session

Hello everyone, Following command sends word 'test' followed by an enter into a screen session (in our case screen_1). How do I print the result, if that would result ? How do I print the result, even if the program running in the session is locked ? Thank you :) screen -S screen_1 -X... (5 Replies)
Discussion started by: akula_1986
5 Replies

9. Shell Programming and Scripting

Print variable on screen

Hi, I've stored the output of a command into a variable. The variable contains the following output: outputline1 outputline2 outputline3 ... How can I echo the variable so that the output is as follow and not one line: outputline1 outputline2 outputline2 ... Thanks a lot! (4 Replies)
Discussion started by: Sego
4 Replies

10. Shell Programming and Scripting

The pipe not use "tee" to print on the screen for specific function

I have code fragment like { aa bb cc } > $LOG aa bb cc, all call function "ff", I want "ff" to print on the screen,but others do not print on the scree, is there a method? I can't use "tee", becasue tee I meet the write "error" ff() { echo "hello" } (2 Replies)
Discussion started by: yanglei_fage
2 Replies
jfs_fsck(8)						  JFS utility - file system check					       jfs_fsck(8)

NAME
jfs_fsck - initiate replay of the JFS transaction log, and check and repair a JFS formatted device SYNOPSIS
jfs_fsck [ -afnpvV ] [ -j journal_device ] [ --omit_journal_replay ] [ --replay_journal_only ] device DESCRIPTION
jfs_fsck is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any errors found. device is the special file name corresponding to the actual device to be checked (e.g. /dev/hdb1). jfs_fsck must be run as root. WARNING
jfs_fsck should only be used to check an unmounted file system or a file system that is mounted READ ONLY. Using jfs_fsck to check a file system mounted other than READ ONLY could seriously damage the file system! OPTIONS
If no options are selected, the default is -p. -a Autocheck mode - Replay the transaction log. Do not continue fsck processing unless the aggregate state is dirty or the log replay failed. Functionally equivalent to -p. Autocheck mode is typically the default mode used when jfs_fsck is called at boot time. -f Replay the transaction log and force checking even if the file system appears clean. Repair all problems automatically. -j journal_device Specify the journal device. -n Open the file system read only. Do not replay the transaction log. Report errors, but do not repair them. --omit_journal_replay Omit the replay of the transaction log. This option should not be used unless as a last resort (i.e. the log has been severely corrupted and replaying it causes further problems). -p Automatically repair ("preen") the file system. Replay the transaction log. Do not continue fsck processing unless the aggregate state is dirty or the log replay failed. Functionally equivalent to -a. --replay_journal_only Only replay the transaction log. Do not continue with a full file system check if the replay fails or if the file system is still dirty even after a journal replay. In general, this option should only be used for debugging purposes as it could leave the file system in an unmountable state. This option cannot be used with -f, -n, or --omit_journal_replay. -v Verbose messaging - print details and debug statements to stdout. -V Print version information and exit (regardless of any other chosen options). EXAMPLES
Check the 3rd partition on the 2nd hard disk, print extended information to stdout, replay the transaction log, force complete jfs_fsck checking, and give permission to repair all errors: jfs_fsck -v -f /dev/hdb3 Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors: jfs_fsck -n /dev/hda5 EXIT CODE
The exit code returned by jfs_fsck represents one of the following conditions: 0 No errors 1 File system errors corrected and/or transaction log replayed successfully 2 File system errors corrected, system should be rebooted if file system was mounted 4 File system errors left uncorrected 8 Operational error 16 Usage or syntax error 128 Shared library error REPORTING BUGS
If you find a bug in JFS or jfs_fsck, please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site: http://jfs.sourceforge.net/ Please send as much pertinent information as possible, including the complete output of running jfs_fsck with the -v option on the JFS device. SEE ALSO
fsck(8), jfs_mkfs(8), jfs_fscklog(8), jfs_tune(8), jfs_logdump(8), jfs_debugfs(8) AUTHORS
Barry Arndt (barndt@us.ibm.com) William Braswell, Jr. jfs_fsck is maintained by IBM. See the JFS project web site for more details: http://jfs.sourceforge.net/ October 29, 2002 jfs_fsck(8)
All times are GMT -4. The time now is 03:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy