09-30-2010
SSH using the shell on the client side -- possible?
I have identical scripts on two machines: one a laptop running Ubuntu 9.04, and the other a Windows XP desktop running Cygwin. The files I'd like to process are on the Windows machine. Running the script in Cygwin engages eight calls to an external executable and spins off who knows how many forks and child processes -- the end-up is that it's as slow as a turtle in a half-Nelson negotiating a waterfall. On the Linux box, both with local files and folders and shared folders over my two-machine LAN (hope that rates as one; I don't know what else to call it), it is of course galaxies faster.
I'd prefer not to make every directory I intend to evaluate with this script into a share point, so I was wondering if there was any way to configure SSH or something similar to log into the Windows box and use the Linux shell and system files to run the script.
Looking forward to well-considered answers.
BZT
7 More Discussions You Might Find Interesting
1. Cybersecurity
Eh... yeah. What the title says. :D (1 Reply)
Discussion started by: PSC
1 Replies
2. UNIX for Dummies Questions & Answers
Ive written a java based "webscraper to rss feed" which resides on my college web space when I execute the app from putty it creates the feed and sets the permissions perfectly.I then wrote a php script to execute the app on demand from the browser using
...
system("java -cp... (1 Reply)
Discussion started by: gleesonger
1 Replies
3. UNIX for Advanced & Expert Users
Folks,
I am trying to solve the following problem. I have a process on machine A running as root that needs to mount and access an NFS partition being exported from machine B.
However, I cannot have 'no_root_squash' option given on B, hence I see NFS requests from machine A end up as 'nobody'... (1 Reply)
Discussion started by: helpmelearn
1 Replies
4. AIX
I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server
I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
Discussion started by: massdesign
1 Replies
5. Red Hat
When i tried to mount the nfs i see this error message
mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount
mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied
and the /etc/exports file in the host side looks like this
/remote/proj1 ... (12 Replies)
Discussion started by: srinathk
12 Replies
6. Programming
Hi guys,
I have two questions about acknowledgement in client side with JMS and AMQP:
1. what happens if we set CLIENT_ACKNOWLEDGE in producer side in JMS?
2. if basic.publish finishes executing and there is no exception thrown, this means message has been received in message server? or we... (0 Replies)
Discussion started by: majid.merkava
0 Replies
7. AIX
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies
LEARN ABOUT MOJAVE
platform::shell
platform::shell(n) Tcl Bundled Packages platform::shell(n)
__________________________________________________________________________________________________________________________________________________
NAME
platform::shell - System identification support code and utilities
SYNOPSIS
package require platform::shell ?1.1.4?
platform::shell::generic shell
platform::shell::identify shell
platform::shell::platform shell
_________________________________________________________________
DESCRIPTION
The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.
This package allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
requirement is that the other shell (identified by its path), is actually executable on the current machine.
While for most platform this means that the architecture of the interrogated shell is identical to the architecture of the running shell
this is not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.
For applications like a code repository it is important to identify the architecture of the shell which will actually run the installed
packages, versus the architecture of the shell running the repository software.
COMMANDS
platform::shell::identify shell
This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.
platform::shell::generic shell
This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.
platform::shell::platform shell
This command returns the contents of tcl_platform(platform) for the specified Tcl shell.
KEYWORDS
operating system, cpu architecture, platform, architecture
platform::shell 1.1.4 platform::shell(n)