Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2007
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2007

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: accessing a kernel on a network

  • To: mathgroup at smc.vnet.net
  • Subject: [mg74117] Re: accessing a kernel on a network
  • From: ikantian at yahoo.com
  • Date: Sun, 11 Mar 2007 06:03:13 -0500 (EST)
  • References: <esgpp0$l43$1@smc.vnet.net><eslsmk$q4h$1@smc.vnet.net>

Thx Michael.
So if I simply want to use a kernel running on another machine on my
LAN, I assume I will need no SSH or RSH and so this will be as
straightforward as finding the name (& password if necessary) of the
kernel machine, no?


On Mar 7, 12:21 am, "Michael Weyrauch" <michael.weyra... at gmx.de>
wrote:
> Hello,
>
>    of course, you can attach a local notebook to a remote kernel. This
> is done e.g. via the "Kernel>Kernel Configuration Options" from the local
> frontend. But depending on your details there are other methods as well.
>
> In the "Kernal Properties" you then configure your connection. This, however,
> can be somewhat tricky, and depends on your local conditions, like the
> type of operating system you have on the remote machine, the connectivity software,
> eg. SSH or RSH, various password settings and the like. I suggest you
> need to talk to a local network expert to find out the details in order to set up
> the "Remote shell command". Generically it is rather difficult to help here.
>
> Much information you find in the FAQ on the Wolfram website as well as in
> this newsgroup.
>
> Regards,
> Michael Weyrauch
>
> This is done
> <ikant... at yahoo.com> schrieb im Newsbeitragnews:esgpp0$l43$1 at smc.vnet.net...
>



  • Prev by Date: Re: Synergetics coordinates NoteBooks
  • Next by Date: Re: workbench and java 1.6 ??
  • Previous by thread: Re: accessing a kernel on a network
  • Next by thread: Re: accessing a kernel on a network