Re: Piping output to a file
> pipes output to a file, >> appends to the end of that file. Bill Evans UNIX System Administrator (719)535-4194 AIM bievans4194 The recognized global leader in ensuring clients achieve superior value in the global economy. -Original Message- From: David Browne. [mailto:[EMAIL PROTECTED]] Sent: Friday, December 28, 2001 5:24 AM To: [EMAIL PROTECTED] Subject: Piping output to a file I know there is a command to pipe information out to a file, but what I need to be able to do is append information on. For example can someone tell me how I could append a manual backups information into my schedule log without overwriting the scheduled backup information?
Re: Piping output to a file
what you will find is that "dsmc" doesn't like to process > or >> what you will need to do is use "eval" such as eval dsmc incr -pass=blah >> /somepath/sched.log or eval nohup dsmc incr -pass=blah >> /somepath/sched.log & that should work for you... later, Dwight -Original Message- From: David Browne. [mailto:[EMAIL PROTECTED]] Sent: Friday, December 28, 2001 6:24 AM To: [EMAIL PROTECTED] Subject: Piping output to a file I know there is a command to pipe information out to a file, but what I need to be able to do is append information on. For example can someone tell me how I could append a manual backups information into my schedule log without overwriting the scheduled backup information?
Piping output to a file
I know there is a command to pipe information out to a file, but what I need to be able to do is append information on. For example can someone tell me how I could append a manual backups information into my schedule log without overwriting the scheduled backup information?
