This is a discussion on Re: Testing wanted: OpenSSH 4.8 within the OpenSSH Development forums, part of the Networking and Network Related category; On Sat, Mar 15, 2008 at 21:48:26 +0200, Roumen Petrov wrote: > Corinna Vinschen wrote: > > On ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Sat, Mar 15, 2008 at 21:48:26 +0200, Roumen Petrov wrote:
> Corinna Vinschen wrote: > > On Mar 15 09:23, Damien Miller wrote: > >> On Thu, 13 Mar 2008, Tim Rice wrote: > >> > >>> On Thu, 13 Mar 2008, Damien Miller wrote: > >>> > >>>> Either way, please try this diff: > >>>> - *) PLINK=`which ${TEST_SSH_PLINK}` ;; > >>>> + *) PLINK=`which ${TEST_SSH_PLINK} 2>/dev/null` ;; > >>> You can not expect which to be on all platforms. > >> We already use `which` for determining an absolute path to sshd in > >> test-exec.sh. Do you have an alternative? > > > > Shouldn't all POSIX compliant shells understand `type -p <cmd>'? > > > > > > Corinna > > > > > in ksh: > $ type -p ssh > ssh is a tracked alias for /usr/bin/ssh > > in ash: > $ type -p ssh > -p: not found > ssh is /usr/bin/ssh > > > If "which" is problem on some platforms may be "command -v" work on them ? > > Roumen Of the platforms I have access to, it looks like 'command -v' would work. For example, Solaris and AIX have a /bin/command shell script that does the right thing. Of course, there may still be OS's out there where 'command -v' does not work. -- Iain Morgan _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@mindrot.org https://lists.mindrot.org/mailman/li...enssh-unix-dev |