Does anyone know why Avaya refused to give root access to the utlity server?
Or at least why the 46xxsettings.txt file located in /var/www/html has to be owned by root making it impossilble to scp a update version to the server.
Using the web interface is ok if you only have a couple of boxes. What happens when you have 100's or a thousand. Are you really expected to manual log into each web interface to make a simple update?
My wish for Christmas is root access or making 46xxsettings.txt writable by 'admin'
then you could.....
Example
server.list.txt - which contains x number of ip's on indivudual line representing your utility servers.
192.168.1.10
192.168.1.20
192.168.1.30
192.168.1.40
192.168.1.50
192.168.1.60
192.168.1.70
192.168.1.80
192.168.1.90
192.168.1.100
46xx-update-script.sh - parse thru master 46xx file and change IP. upload file. continue
#!/bin/bash
SERVERLIST=server.list.txt
while read serverip || [[ -n $serverip ]]; do
sed s/search-for-this-string/$SERVER_IP/g 46xxsettings-master.txt | tee 46xxsettings.txt > /dev/null
scp -o "LogLevel quiet" 46xxsettings.txt admin@$serverip:/var/www/html
done <$SERVERLIST
*ideally you would add in some error checking and logging, but off the cuff this appears it would work only if....
Interested in knowing how other people manage large numbers of sites. Seems designed to be labor intensive when it could be so simple.
David
Or at least why the 46xxsettings.txt file located in /var/www/html has to be owned by root making it impossilble to scp a update version to the server.
Using the web interface is ok if you only have a couple of boxes. What happens when you have 100's or a thousand. Are you really expected to manual log into each web interface to make a simple update?
My wish for Christmas is root access or making 46xxsettings.txt writable by 'admin'
then you could.....
Example
server.list.txt - which contains x number of ip's on indivudual line representing your utility servers.
192.168.1.10
192.168.1.20
192.168.1.30
192.168.1.40
192.168.1.50
192.168.1.60
192.168.1.70
192.168.1.80
192.168.1.90
192.168.1.100
46xx-update-script.sh - parse thru master 46xx file and change IP. upload file. continue
#!/bin/bash
SERVERLIST=server.list.txt
while read serverip || [[ -n $serverip ]]; do
sed s/search-for-this-string/$SERVER_IP/g 46xxsettings-master.txt | tee 46xxsettings.txt > /dev/null
scp -o "LogLevel quiet" 46xxsettings.txt admin@$serverip:/var/www/html
done <$SERVERLIST
*ideally you would add in some error checking and logging, but off the cuff this appears it would work only if....
Interested in knowing how other people manage large numbers of sites. Seems designed to be labor intensive when it could be so simple.
David
Comment