On Thursday 30 December 2004 11:51, Alexandr Malusek wrote:
steve <mail@steve-ss.com> writes:
Just being lazy. It's such a pain having to install a new app. on every one of our 20 clients. I've never found a satisfactory script to help so I walk around to each client and do it by hand.
I use simple scripts like
#!/bin/bash set -x NODES="pi1 pi2 pi3 pi4 pi5 pi6 pi7" for node in $NODES; do ssh $node "$@" done
It runs the argument on each client:
# ./run_on_nodes "rpm -qa | head -1" + NODES=pi1 pi2 pi3 pi4 pi5 pi6 pi7 + ssh pi1 'rpm -qa | head -1' kdeartwork3-sound-3.2.1-53 + ssh pi2 'rpm -qa | head -1' kdeartwork3-sound-3.2.1-53 ...
That is enough to steer me in the right direction. Thanks. It's just that working away from NT or 2000 you really have no idea how people do things anymore, a big disadvantage for leaving Microsoft safety.
Back to the server specification: it's up to you to do some measurements to estimate what server you need. Or you can ask a company to do it for you. We can mention some tricks (e.g. to export NFS filesystems with the async and read-only options) but it's hard to give specifications without knowing the machines you have, their load, the network load, ...
You are correct of course. I should give more details. We have a amd 2200 server with 1024 Mb. This is a nfs server for /home rw to 23 PII 450 clients using NIS. 9.2 is local on all disks. All clients use kdm to log into kde. Works fine so far. I've done all the async/autofs/8192 tricks I can lay my hands on. Here goes with a typical bottleneck: I have a lesson using OOo draw and we are all going to start OOo at the same time, reload the flow diagram we started last lesson save it every 5 or so minutes, cut maybe a diagram from a website in konq and paste it in. Exporting /usr and /home or using ssh to run the app on the server is, to put it politely, a joke. Unless you have only 2 clients of course where it runs perfectly. But we don't :-( Cheers, Steve.