Hi there
I know that this isn't the place to put a question like this i supose, but i'm geting desperated. I have searched in interbase forums and nothing helped. If anyone can help me i would apreciated.
I'm using HP-UX with a version 3 of interbase wich means i can't split the backup file into... (3 Replies)
Operating system - Solaris 8, Korn shell, xterm
Command
/usr/proc/bin/ptree
outputs the process tree exactly as I want with all detail
However,
/usr/proc/bin/ptree | more
truncates the process descriptions at an 80 character point. If the process tree has marched enough to the right,... (3 Replies)
Hiya all,
Simple question - yet no simple answer im afraid !
Is there a way to execute a shell script (child) which returns one line and get the current (parent) shell to execute the stdout from the child ???
example
child.sh
#!/bin/sh
echo "setenv DISPLAY xxx:03"
parent_prompt>... (5 Replies)
Does anyone know how I can use gzip to zip a large log file on the fly.
My simulation is currently logging a large file that I need for analysis at a later point. However the files are so huge that I may even run out of disk space. The content is mainly text so when compressed the files are... (2 Replies)
Hi,
as part of a script i have a loop that goes though a set of files.
This loop can take some time, so i'd like to show the user that something is happening by showing them the filename being worked on.
I could create a long list of file names in the terminal using echo or print... (0 Replies)
I want to split big files based on a pattern to stdout.
Although csplit works well for me splitting the output into separate files (e.g. xx00, xx01, xx02, ...), the following is not working as expected:
<code>
# assuming pattern occurs less than 100 times
csplit bigfile '%pattern%'... (2 Replies)
Can somebody explain to me why the diff output is not going to stderr?
Yet when I issue a diff from the command line the return code is -ne 1.
I am guessing diff always writes to stdout???
Is there away I can force the difff to write to stderr USING THE CURRENT
template. If possible, I... (5 Replies)
Hi
Is there way to, say, echo a line and make sure it is always displayed on the first line, no matter what is coming out on stdout?
eg:
#!/bin/bash
clear
echo " ...... Internal audit script ......"
tar xvf hugefile.tar
I'd like to have the " Internal audit script " line to be shown... (2 Replies)
Hi,
I have a program set to read in a text file, change certain characters and then print the altered version to the screen but does anyone know how to save the new version as another text file? And, if possible, how to specify the file name, and perhaps location?
Thanks! (2 Replies)
Discussion started by: PerlNutt
2 Replies
LEARN ABOUT FREEBSD
atf-test-program
ATF-TEST-PROGRAM(1) BSD General Commands Manual ATF-TEST-PROGRAM(1)NAME
atf-test-program -- common interface to ATF test programs
SYNOPSIS
atf-test-program [-r resfile] [-s srcdir] [-v var1=value1 [.. -v varN=valueN]] test_case
atf-test-program -l
DESCRIPTION
Test programs written using the ATF libraries all share a common user interface, which is what this manual page describes. NOTE: There is no
binary known as atf-test-program; what is described in this manual page is the command-line interface exposed by the atf-c, atf-c++ and
atf-sh bindings.
In the first synopsis form, the test program will execute the provided test case and print its results to the standard output, unless other-
wise stated by the -r flag. Optionally, the test case name can be suffixed by ':cleanup', in which case the cleanup routine of the test case
will be executed instead of the test case body; see atf-test-case(4). Note that the test case is executed without isolation, so it can and
probably will create and modify files in the current directory. To execute test cases in a controller manner, you need a runtime engine that
understands the ATF interface. The recommended runtime engine is kyua(1). You should only execute test cases by hand for debugging pur-
poses.
In the second synopsis form, the test program will list all available test cases alongside their meta-data properties in a format that is
machine parseable. This list is processed by kyua(1) to know how to execute the test cases of a given test program.
The following options are available:
-l Lists available test cases alongside a brief description for each of them.
-r resfile Specifies the file that will receive the test case result. If not specified, the test case prints its results to stdout. If
the result of a test case needs to be parsed by another program, you must use this option to redirect the result to a file
and then read the resulting file from the other program. Note: do not try to process the stdout of the test case because
your program may break in the future.
-s srcdir The path to the directory where the test program is located. This is needed in all cases, except when the test program is
being executed from the current directory. The test program will use this path to locate any helper data files or utilities.
-v var=value Sets the configuration variable var to the value value.
SEE ALSO kyua(1)BSD March 2, 2014 BSD