Off-Topic > Off-Topic - Tiny Core Lounge
How to netwrok several TinyCore workstations and a server?
ananix:
using ssh sounds more like a distributed computing solution.
The server that holds the batch jobs executes them on the remote nodes and they log to the server syslog which in return can act upon the different status of the nodes and their jobs.
Thats diffidently also an approach, but it sounds like the program setup is already decided only the tools are needed. Besides that its stated we are talking batch in that case only the location of the job data is interesting in regards to nfs.
PS I have failed to mention that my experience is that NFS needs a reliable network connection as it locks the terminal for æons when trying to access a dead mount and also when booting offline but you can work out the setup to fit your scenario.
Anubis:
Folks I would like to thank you all again for your help.
BTW due to NDA I can't be as open as I would like to.
I will try to detail a bit more what was requested from me.
We have regular desktops where I would say MiniCore Linux runs (no GUI just CLI) booting of USB drives.
The systems are used to test a piece of hardware (add on card) in house programmers make a batch file that provides the operater with multiple settings that pick the specific executable and passes on some parameters.
My guess was trowing this main folder and booting of a minimal mini-core that would mount upon boot the share/exported folder as something local. For this reason I don't think ssh would work.
I could be wrong.
The test diagnostics software has to run on the local workstation and be able to access the hardware.
Would a ssh session not run the diagnostic program against the server's hardware? Would using NFS be any different?
I have been reading some other posts regaring NFS on Tiny/Minicore 4 and there seems to be issues with it. Not so with Tiny/Mini core 3.
Again, you guys have been great.
tinypoodle:
ssh is not suitable for running apps locally.
In order to transfer files, both scp and ftp could be used - ftpget/ftpput (client) is already in base, scp would require the dropbear or openssh extension.
gerald_clark:
I use NFS extensively with TC. There is nothing wrong with it.
curaga:
So if I read that right, you only need to get the latest software from the server each boot, and then send back results?
If so, then NFS might be a bit heavy for that use, and any file serving solution from FTP, TFTP, SCP, etc will work.
On the other hand, if the clients need to see updates while live, then NFS is exactly what you need.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version