Net::SSH Help?

2001-02-13 Thread Martin Moss

Hi everyone,

Has anybody had any experience with using Net::SSH?

Am trying to implement a CVS system (was going to use VCS::CVS), but just
been told we're only allowing ssh across all our servers, so I need to find
a replacement for telnet and FTP. So basically I'm looking for any scripts
or advice on using perl to send ssh/scp commands.

Regards

Marty


___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users



Re: File tests

2001-02-13 Thread Lee Goddard

perldoc -f -f says:  -f  File is a plain file.
So, it won't see the binary MP3s.

hth
lee

Justin Ko wrote:
 
 Hey everyone,
 Has anyone noticed weird behavior of the file test ( -f ) in ActivePerl
 v5.6.0.620
 Maybe it's just because I am new to this whole perl thing, but it doesn't
 seem to be actually testing for files. I'd pass it some text files and some
 MP3's, and it wouldn't return true for them. What am I doing wrong?
 
 -Justin Ko
-- 

Lee Goddard [EMAIL PROTECTED]
-
Perl : XML : XSLT : XHTML / JS : Java

"Post-modernismthe meta-narrative that denies meta-narrative."
   - Cedric Watts, Sussex 1997
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users



Re: Perl App or something similar .. . . . .

2001-02-13 Thread Alexander F. Gutfeldt

On Mon, 12 Feb 2001,  Jan Dubois wrote:

On that subject, does PerlApp create smaller executables than Perl2Exe?

No, they are about the same size.  PerlApp already has the -small and
-tiny option that you only get with the Pro version of Perl2Exe.

AFAIR Perl2Exe produces (automagic) a bunch of DLLs for the
modules/packages I require/use in my projects when I use the -tiny
option.

How do I achieve a similar result using PerlApp? 


___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users



Re: File tests

2001-02-13 Thread $Bill Luebkert

Lee Goddard wrote:
 
 perldoc -f -f says:  -f  File is a plain file.
 So, it won't see the binary MP3s.

I think binary files still fall under the plain/regular file category.
Links, pipes, dirs, special files and sockets don't.

-- 
  ,-/-  __  _  _ $Bill Luebkert   ICQ=14439852
 (_/   /  )// //   DBE Collectibles   http://www.todbe.com/
  / ) /--  o // //  Mailto:[EMAIL PROTECTED] http://dbecoll.webjump.com/
-/-' /___/__/_/_http://www.freeyellow.com/members/dbecoll/
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users



Re: Net::SSH Help?

2001-02-13 Thread Steven Wadding

At 11:56 AM 2/13/01 +, Martin Moss wrote:
Has anybody had any experience with using Net::SSH?

Am trying to implement a CVS system (was going to use VCS::CVS), but just
been told we're only allowing ssh across all our servers, so I need to 
find
a replacement for telnet and FTP. So basically I'm looking for any scripts
or advice on using perl to send ssh/scp commands.

I know there's also a Net::SCP module, which needs Net::SSH to be 
installed.  I expect to have to use it soon, but haven't got that far 
yet.

Steve W.

___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users



Re: Path in autoexec.bat

2001-02-13 Thread Will W

This seems more OSish than Perlish, but there is certainly a tie to
perl...

Back in a younger day, when DOS v3.3 ruled, we all found that appending
to PATH was dicey since whether it worked depended on whether the last
guy to do so put a terminating ";" in place. Otherwise, silent failures.
It was easier to prepend with an assured ";" at the tail of our own
addition than to use the batch file tools to determine whether a
trailing ";" was present (nobody wanted to waste precious bytes with
unnecessary ";"s-- we only had 127 chars for the entire path statement,
which was tight on those early networks).

Did you check whether the PATH causing the failure has semicolons in all
the right places? You may yet have other problems in your configuration.

- Original Message -
From: Sisyphus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 13, 2001 4:36 AM
Subject: Path in autoexec.bat


 Hi,
 When I first installed perl on my PC I was unable to run perl scripts
by
 entering at the prompt:
 perl somefile.pl
 Instead I had to specify the path to the perl interpreter. So, to run
 somefile.pl I would enter:
 \perl\bin\perl somefile.pl

 This was the case, even though the 'PATH' variable contained the
setting
 'C:\PERL\BIN;'

 It wasn't until I added 'SET PATH=C:\PERL\BIN;%PATH%' to the
autoexec.bat
 file that I was able to run scripts by entering:
 perl somefile.pl

 Can someone explain this to me - why was the 'PATH' setting, by
itself,
 unable to provide the functionality I was after ? What functionality
does it
 provide ?
 And does that 'PATH' setting (in regards to perl) currently serve any
useful
 purpose now that 'SET PATH' is specified ?
 Things are now working fine - but these questions still bug me.

 I should add that the scripts I was running were not being run from
the root
 directory (ie. I'd first 'cd' to the directory in which the scripts
were
 saved, and run them from that directory). I mention that in case it's
 relevant.

 Cheers,
 Rob
 Visit our website at http://www.kalinabears.com.au

 ___
 Perl-Win32-Users mailing list
 [EMAIL PROTECTED]
 http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users


___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users



Re: Path in autoexec.bat

2001-02-13 Thread Sisyphus

Hi Will,
There was no semi-colon at the end of the line - but I don't think one is
required there. However, I did notice that there was one white space
occurring before 'PATH'. Could that be it ? Are you telling me that the
'PATH' specification should be sufficient and that I should not need the
'SET PATH' setting ?
DOS 3.3 ? I've got 4.something.  ( I believe they are both fully documented
in the 'Dead Sea Scrolls'. )

Cheers,
Rob
Visit our website at http://www.kalinabears.com.au
- Original Message -
From: Will W [EMAIL PROTECTED]
To: Sisyphus [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2001 12:59 AM
Subject: Re: Path in autoexec.bat


 This seems more OSish than Perlish, but there is certainly a tie to
 perl...

 Back in a younger day, when DOS v3.3 ruled, we all found that appending
 to PATH was dicey since whether it worked depended on whether the last
 guy to do so put a terminating ";" in place. Otherwise, silent failures.
 It was easier to prepend with an assured ";" at the tail of our own
 addition than to use the batch file tools to determine whether a
 trailing ";" was present (nobody wanted to waste precious bytes with
 unnecessary ";"s-- we only had 127 chars for the entire path statement,
 which was tight on those early networks).

 Did you check whether the PATH causing the failure has semicolons in all
 the right places? You may yet have other problems in your configuration.

 - Original Message -
 From: Sisyphus [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Tuesday, February 13, 2001 4:36 AM
 Subject: Path in autoexec.bat


  Hi,
  When I first installed perl on my PC I was unable to run perl scripts
 by
  entering at the prompt:
  perl somefile.pl
  Instead I had to specify the path to the perl interpreter. So, to run
  somefile.pl I would enter:
  \perl\bin\perl somefile.pl
 
  This was the case, even though the 'PATH' variable contained the
 setting
  'C:\PERL\BIN;'
 
  It wasn't until I added 'SET PATH=C:\PERL\BIN;%PATH%' to the
 autoexec.bat
  file that I was able to run scripts by entering:
  perl somefile.pl
 
  Can someone explain this to me - why was the 'PATH' setting, by
 itself,
  unable to provide the functionality I was after ? What functionality
 does it
  provide ?
  And does that 'PATH' setting (in regards to perl) currently serve any
 useful
  purpose now that 'SET PATH' is specified ?
  Things are now working fine - but these questions still bug me.
 
  I should add that the scripts I was running were not being run from
 the root
  directory (ie. I'd first 'cd' to the directory in which the scripts
 were
  saved, and run them from that directory). I mention that in case it's
  relevant.
 
  Cheers,
  Rob
  Visit our website at http://www.kalinabears.com.au
 
  ___
  Perl-Win32-Users mailing list
  [EMAIL PROTECTED]
  http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
 


___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users