Sponsored Content
Full Discussion: Verifying C++ program
Top Forums Programming Verifying C++ program Post 302088421 by jim mcnamara on Tuesday 12th of September 2006 09:35:28 AM
Old 09-12-2006
Since you didn't specify a platform, or very much else - here is a list of what is out there. You decide what you want and what you will/won't pay for:

http://en.wikipedia.org/wiki/List_of..._code_analysis
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Verifying sting format in bash

Hello, This one has me stumped, although I suspect it might be easy. I have a file and need to split the entries into two varaibles. The format for a positive is 'AANNNN' where A is alpha and N is numeric. Thanks in advance (5 Replies)
Discussion started by: 98_1LE
5 Replies

2. HP-UX

Verifying remote command status

hello Friends, I wanted to verify status of remote command executed on remote machine in hpux. remsh <hostname> -l root cd /sampldir i wanted to check weather the command executed on remote machine correctly or not by $?. Can you tell me how to execute multiple command on remote machine. ... (0 Replies)
Discussion started by: ravikiran
0 Replies

3. UNIX for Dummies Questions & Answers

verifying tape backups

Hello all, how would i go about verifying that a tape is backing up data correctly other than restoring the backup. for example, what command would i use to check the tape for errors? Any and all help is appreciated -Coffee (0 Replies)
Discussion started by: coffeebrown
0 Replies

4. HP-UX

Verifying backup on Tru64

Hy everyone and happy new year! I would like to know how can i verify that some of my backup tapes, created with vdump, are ok? Some of them were created before i came to the company that i'm workin for now, so i would like to test them before i actually use them. Unfortunately, i don't have... (0 Replies)
Discussion started by: veccinho
0 Replies

5. Shell Programming and Scripting

Verifying SSH connectivity in a script

Hi everyone, I'm trying to write a korne shell script that takes the IP address of a remote server as an argument and logs into that server if RSA key has been setup properly, otherwise exits if RSA key is not set for that server. I don't want the script to get stuck with Password prompt... (1 Reply)
Discussion started by: omd
1 Replies

6. Shell Programming and Scripting

Verifying killall command usage

killall -KILL rdiff-backup Is it a valid command coz i couldn't find a -KILL option for killall in the man page. (1 Reply)
Discussion started by: proactiveaditya
1 Replies

7. Shell Programming and Scripting

Verifying table records

Hi, Script copies records of two tables into another tables for backup before using oracle's import utility to restore from backup. Now, suppose if the import utility fails then the script will again copy those records from the backup table to the original ones. How to check whether all... (2 Replies)
Discussion started by: milink
2 Replies

8. Solaris

Verifying LPD is running

Apologies in advance, I'm usually a Linux admin so I'm not well versed in Solaris administration. In Linux there's usually an lpd executable running and you can check the process list for it to do a high level check on the state of the printing subsystem. Is the executable called the same in... (1 Reply)
Discussion started by: thmnetwork
1 Replies

9. Shell Programming and Scripting

Verifying Record Length

Hi all, We are going through a total migration from AIX-based server framework to Linux-based servers. When I am testing *.sh and *.awk in a lower environments, it abends at the same step everytime in verifying the record length of the first row of the source file. I know this source file... (11 Replies)
Discussion started by: SoloXX
11 Replies
tee(1)							      General Commands Manual							    tee(1)

NAME
tee - Displays the output of a program and copies it into a file SYNOPSIS
tee [-ai] file... STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: tee: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Adds the output to the end of file instead of writing over it. Ignores the SIGINT signal. OPERANDS
Standard input is stored into, or appended to, the file specified. [Tru64 UNIX] The tee command can accept up to 20 file arguments. DESCRIPTION
The tee command reads standard input and writes to both standard output, and each specified file. The tee command is useful when you wish to view program output as it is displayed, and also want to save it in a file. The tee command does not buffer output, so you may wish to pipe the output of tee to more if more than one full screen of data is anticipated. NOTES
If a write to any file fails, the exit status of tee will be non-zero. Writes to all other specified files may be successful, and opera- tion will continue until standard input is exhausted. EXIT STATUS
The following exit values are returned: Successful completion. An error occurred. EXAMPLES
To view and save the output from a command at the same time, enter: lint program.c | tee program.lint This displays the standard output of the command lint program.c at the terminal, and at the same time saves a copy of it in the file program.lint. If program.lint already exists, it is deleted and replaced. To display and append to a file, enter: lint program.c | tee -a program.lint This displays the standard output of lint program.c at the terminal and at the same time appends a copy of it to the end of pro- gram.lint. If the file program.lint does not exist, it is created. ENVIRONMENT VARIABLES
The following environment variables affect the execution of tee: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: cat(1), echo(1), script(1) Standards: standards(5) tee(1)
All times are GMT -4. The time now is 07:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy