Hi, Meybe there is another solution.
Initaly I didn't want to generate private/public keys, because I was planning to use the root account. But, to solve this security issue, I create a user account with user rights, and generate ssh private/public keys (less dangerous that root account) I add command provileges to sudoers, so the account can run a script that will : - transfert needed files overs overs ssh to other servers - run make command to create the db files on all servers What do you think about this solution ? Luis Luis Esteves wrote: > > Hi everybody, > > In our organisation we have 4 postfix servers. > Each time i need to add a new configuration to the transport file (for a > new domain), i need to update the transport file on each server. > This is cumbersome. Connect on each server with ssh, update the transport > file, et run make to generate a db file. > > Is there an easy way to update all files on each server easily (without > generating ssh public/private keys and running these commands from one > server) ? > > Is it a good idea to use a centralized PostgreSQL database to store the > Postfix configuration files ? > > Thanks, > Luis > -- View this message in context: http://old.nabble.com/Update-Postfix-transport-file-on-multiple-servers-tp31008507p31061754.html Sent from the Postfix mailing list archive at Nabble.com.
