I was reviewing a shell script and I found this line:
I have tried removing the >> directive and all that will occur is that the file will be created--nothing gets put in the file. If I put back the >> directive it works. If I remove the > the line fails. Why are both >> and > required?
Is there a general rule I can apply when examining/editing ipfw entries?
Also, does each new entry have to have a unique rule number?
And, I think I can write a script to block code red infected machines (though I'm not sure it would do more than slim down my web server error message log),... (0 Replies)
Hello,
Is there anyway to prevent users from modifying limits imposed by php.ini configuration in a phpSuExec configured PHP installation??
For example in server with PHP running in a module, I use php_admin_* directives:
php_admin_value memory_limit 40M
And users can't modify them... (0 Replies)
Hi,
I have a script below. It get's the data from the output of a script that is running hourly. My problem is every time my script runs, it deletes the previous data and put the current data. Please see output below. What I would like to do is to have the hourly output to be appended on the... (3 Replies)
I am running a command which has a parameter that outputs the results to a file each time it is run.
Here is the command:
--fullresult=true > importlog.xml
Can I add the output to the file rather than creating a new one which overwrites the existing one?
If not can I make the file name... (2 Replies)
Hi experts
i have a simple script that fetches the count from different servers and inserts ahead of server name like below
servera,1
serverb,25
serverc,35
what i want to do is now when i run this script next day i want that output to be next to the earlier one like below and if possible... (5 Replies)
Hi All, can you help me with this:
grep XXX dir/*.txt|wc -l > newfile.txt - this put the results in the newfile.txt, but I want to add another column in the newfile.txt, string 'YYYYY', separated somehow, which corresponds on the grep results?
For example grep will grep XXX dir/*.txt|wc -l >... (5 Replies)
Hi there,
I have 2 fairly simple lines I am running and both work as expected, but I am trying to append the two of them to output a single line.
The first command get the MAC times of each file :-
find /media/Vista/Garmin/PCBSMP2/ -type f -printf "%A+ (a) %p\n%T+ (m) %p\n%C+ (c) %p\n"
... (9 Replies)
Hello,
i'm trying to force a command to read every second from an interface
watch -n1 (command) /dev/x | cat >> output
but it continue to overwrite the file, without append the content
Thanks and advace for help as usual
regards (4 Replies)
I am currently using Linux CentOS and programming in FORTRAN 90 using Portland 7.1 compiler.
I am able to set in the preprocessor directives a flag called TEST. when I go to use logic in my code i can write
#ifdef TEST
execute something
#endif
Furthermore, if I want to negate the... (2 Replies)
input1
john 20
bob 30
input2
john 60
bob 100
cat input1 >> output
cat input2 >> output
ouput
john 20
bob 30
john 60
bob 100
desired output
input1 input1 input2 input2
john 20 john 60 (3 Replies)
Discussion started by: quincyjones
3 Replies
LEARN ABOUT OPENSOLARIS
tee
tee(1) User Commands tee(1)NAME
tee - replicate the standard output
SYNOPSIS
/usr/bin/tee
/usr/bin/tee [-ai] [file]...
ksh93
tee [-ail] [file]...
DESCRIPTION
/usr/bin/tee
/usr/bin/tee copies standard input to standard output, making a copy in zero or more files. tee does not buffer its output. The options
determine if the specified files are overwritten or appended to.
ksh93
The tee built-in in ksh93 is associated with the /bin and /usr/bin paths. It is invoked when tee is executed without a pathname prefix and
the pathname search finds a /bin/tee or /usr/bin/tee executable.
tee copies standard input to standard output and to zero or more files. The options determine whether the specified files are overwritten
or appended to. The tee utility does not buffer output. If a write to a file fails, tee continues to write to other files although it exits
with a non-zero exit status.
The number of file operands that can be specified is limited by the underlying operating system.
OPTIONS
/usr/bin/tee
The following options are supported by /usr/bin/tee:
-a Appends the output to the files rather than overwriting them.
-i Ignores interrupts.
ksh93
The following options are supported by the tee built-in command in ksh93:
-a Appends the output to the files rather than overwriting them.
--append
-i Ignores SIGINT signal.
--ignore-interrupts
-l Sets the standard output to be line buffered.
--line-buffer
OPERANDS
The following operands are supported:
file A path name of an output file. Processing of at least 13 file operands are supported.
USAGE
See largefile(5) for the description of the behavior of tee when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of tee: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
EXIT STATUS
/usr/bin/tee
The following exit values are returned by /usr/bin/tee:
0 The standard input was successfully copied to all output files.
>0 The number of files that could not be opened or whose status could not be obtained.
ksh93
The following exit values are returned by tee in ksh93:
0 Successful completion.
>0 An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
/usr/bin/tee
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|Standard |See standards(5). |
+-----------------------------+-----------------------------+
ksh93
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |See below. |
+-----------------------------+-----------------------------+
The ksh93 built-in binding to /bin and /usr/bin is Volatile. The built-in interfaces are Uncommitted.
SEE ALSO cat(1), ksh93(1), attributes(5), environ(5), largefile(5), standards(5)SunOS 5.11 20 Nov 2007 tee(1)