HIPL

hipfw hipd independency

Asked by Andrius Bentkus

I thought that hipfw should work without hipd, but when the configuration files are not present it emits a lot of errors which suggest that hipd should be running too, or am I wrong?

Question information

Language:
English Edit question
Status:
Answered
For:
HIPL Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Miika Komu (miika-iki) said : 		#1

Hipd has to be started once on the host to create the configuration files. The functionality to create the config files could be wrapped behind a single function and executed from the hipfw as well. However, then we should have some kind of locking to avoid race conditions where hipd and hipfw are started simultaneously.

Revision history for this message
René Hummen (rene-hummen) said : 		#2

IMHO, we should provide our default configs as separate text files in our repository and copy them on "make install" / use them for packaging. I don't see a good reason why to keep the default config as part of the code. This would also remove the need for additional functionality in the firewall and the race condition you were describing.

Revision history for this message
Miika Komu (miika-iki) said : 		#3

The reason why it was added to the code was to remove the need for "make install". How is this handled in other daemon software?

Can you help with this problem?

Provide an answer of your own, or ask Andrius Bentkus for more information if necessary.

To post a message you must log in.