Hmmm... looks like I'm going to stumble over host-specific parts of pf.conf
(e.g. hostname and interfaces) mixed with non-host specific parts (e.g. dhcp).
Is there a way to break up this file in 4.0.2? In otherwords is there an
"include" type facility or some sort of macro expansion run on this file? That
would let me put host-specific parts in another location, and then perform
replication on that /usr/local/pf/conf between.
Can anybody think of anything else that my stub my toe on this?
Don
From: Don Greer [mailto:[email protected]]
Sent: Tuesday, July 30, 2013 10:10 AM
To: [email protected]
Subject: [PacketFence-users] Confirmation on behavior of "configfile_add"
I just wanted to confirm that you are no longer using "configfile_add" to
push the parsed config files into the SQL server. It appears that this
behavior has been removed.
The reason is I'm attempting to setup redundancy using a Master-Master
replication of the mysql databases. I need this because the servers will be
geographically distributed and the ability to have two servers with the same IP
(or being to assume the same IP) won't work in our network without some serious
monkeying around of the production network (not an option). In looking at
dumps of the database, I don't see anything that is directly tied to the server
host IP or host name, so it seems like it should work.
Can anybody think of a reason why this will melt down?
Don
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users