#13 Load architecture specific files

[Andrew Ruthven]

I want to have spong-client on a NFS share which is
shared between
multiple architectures. To remove the need to either:
- Have different client trees
- Have architecture dependent info duplicated in each
spong.conf.<host> file

I have modified spong.conf to also attempted to load a
spong.conf.<architecture> file (before the <host>
file).

The patch against spong-client v2.7.7 is attached.

I've modified the output from uname to remove any
potentially
nasty characters (for example, on BSDi 'uname -a'
returns "BSD/OS").
Run:

perl -MPOSIX -e '$name = (uname)[0]; $name =~
s/[^A-Za-z0-9]/_/g; print "$name\n"';

To find out what you should replace <architecture> with
on your system.
Linux boxes use Linux, BSDi use BSD_OS, Solaris 2.4 use
SunOS

[Andrew Ruthven]

Fix the file that should be patched (just add .pl)

[Andrew Ruthven]

Logged In: YES
user_id=10660

I'm setting Spong up at home now and trying to generalise
the config files as much as possible. I've found that this
patch should really be applied to the scripts...

[Andrew Ruthven]

Add architecture specific confg files for spong-network.

[Andrew Ruthven]

Add architecture specific confg files for spong-server