This is just to remind you of the latest rethink in our external
access arrangements, as advertised last week in eduni.dcs.sys.
I've now made the changes advertised below.

Here it is again:

Thanks to all your recent comments, suggestions and reports about
ssh.dcs and external access to dcs.ed.ac.uk machines, we've had a
rethink. This is what we'll do from Monday; we think it addresses all
of your frustrations with the current setup.

ssh.dcs Staff, research postgrads and visitors will be the only
people able to login to this machine. They'll be able to
login from _anywhere_, local or remote.

gateway.dcs Anyone will be able to login to this machine, from
anywhere. But we expect that staff, postgrads and
visitors will prefer to use ssh.dcs.

scar.dcs CS2 upwards can use this machine from ed.ac.uk.

bannocks.dcs CS3 upwards can use this machine from ed.ac.uk.

tweed.dcs This was our recommended "compute server", somewhere
to run big programs so they wouldn't get in the way on
the other multi-user machines. However, tweed is now
not really powerful enough to carry on doing this. So
we're turning it into gateway.dcs (see above) where it
ought to be able to cope, as long as people who use it
show some restraint - e.g. don't run gargantuan hogs
like mozilla on it :-)

ResNet users note: some people seem to have been affected by a problem
whereby they can't login to scar or bannocks from their ResNet
machine. We think that this is a problem with ResNet rather than
anything we're doing. However, if anybody is affected by this, please
contact support@dcs and try to give us data, times and IP addresses.
We'll then check our logs to see if there's any additional information
there to help you tackle the ResNet people.

--
-- Chris.