>I want the following three things to happen when I run p:
>
>1. I want both stdout and stderr to go to the screen
>
>2. I want stdout and stderr combined in a file
>
>3. I want an error log file to only contain stderr.
>
>p 2>&1 | tee outnerr # Solves 1 and 2
>
>p 2> errlog # Solves 3 but b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Steven W. Orr hath spake thusly:
> 1. I want both stdout and stderr to go to the screen
>
> 2. I want stdout and stderr combined in a file
>
> 3. I want an error log file to only contain stderr.
[snip]
> Any takers?
Using on
How about something like this:
p 3>ERR 2>&3 2>&1 | tee OUTERR
Looking at the output of lsof, I think that this is doing the right thing:
cat4157 marc1w FIFO0,0 1092582 pipe
cat4157 marc2w FIFO0,0 1092582 pipe
cat4157
I have a program (which we shall call p) which produces text to both
stdout and stderr.
I want the following three things to happen when I run p:
1. I want both stdout and stderr to go to the screen
2. I want stdout and stderr combined in a file
3. I want an error log file to only contain std
Ken Ambrose <[EMAIL PROTECTED]> writes:
> How do I get logged in to a remote host, via ssh, w/o password prompting,
> a la the rhosts file? I can do it with SSH v1, but v2 seems to give me
> some problems. I've plugged the public key into the authorized_keys file,
> but no dice. Any suggestion
Good morning, Ken,
On Wed, 4 Sep 2002, Ken Ambrose wrote:
> How do I get logged in to a remote host, via ssh, w/o password prompting,
> a la the rhosts file? I can do it with SSH v1, but v2 seems to give me
> some problems. I've plugged the public key into the authorized_keys file,
> but no di
>The most blindly simple-minded approach
>would be the equivalent of:
>
> cat clientMachine:~/.ssh/id*pub >>serverMachine:~/.ssh/authorized_keys
> cat clientMachine:~/.ssh/id*pub >>serverMachine:~/.ssh/authorized_keys2
> chmod go-rwx clientMachine:~/.ssh/authorized_key
The most blindly simple-minded approach
would be the equivalent of:
cat clientMachine:~/.ssh/id*pub >>serverMachine:~/.ssh/authorized_keys
cat clientMachine:~/.ssh/id*pub >>serverMachine:~/.ssh/authorized_keys2
chmod go-rwx clientMachine:~/.ssh/authorized_keys*
Ken Ambrose <[EMAIL PROTECTED]> writes:
> How do I get logged in to a remote host, via ssh, w/o password prompting,
> a la the rhosts file? I can do it with SSH v1, but v2 seems to give me
> some problems. I've plugged the public key into the authorized_keys file,
> but no dice. Any suggestio
On Wed, 4 Sep 2002 [EMAIL PROTECTED] wrote:
>
> In a message dated: Wed, 04 Sep 2002 07:14:31 PDT
> Ken Ambrose said:
>
> >How do I get logged in to a remote host, via ssh, w/o password prompting,
> >a la the rhosts file? I can do it with SSH v1, but v2 seems to give me
> >some problems. I've
On Wed, 2002-09-04 at 10:14, Ken Ambrose wrote:
> How do I get logged in to a remote host, via ssh, w/o password prompting,
> a la the rhosts file? I can do it with SSH v1, but v2 seems to give me
> some problems. I've plugged the public key into the authorized_keys file,
> but no dice. Any sug
In a message dated: Wed, 04 Sep 2002 07:14:31 PDT
Ken Ambrose said:
>How do I get logged in to a remote host, via ssh, w/o password prompting,
>a la the rhosts file? I can do it with SSH v1, but v2 seems to give me
>some problems. I've plugged the public key into the authorized_keys file,
>but
How do I get logged in to a remote host, via ssh, w/o password prompting,
a la the rhosts file? I can do it with SSH v1, but v2 seems to give me
some problems. I've plugged the public key into the authorized_keys file,
but no dice. Any suggestions?
Thanks,
-Ken
__
Jefferson Kirkland said:
> Thanks a bunch for the responses. I had played with the PS1 prompt to
> set it to something different, but will definately try again. Thanks
> again!
I'm running Slackware8.0 and have never had that happen. Just in case you
nolonger have the default prompt part of
14 matches
Mail list logo
