> But how does it work ? who is currently listening for changes in pmxcfs ? > (through inotify?)
>>This is low-level C-code inside pmxcfs (corosync). Please not that INotify >>does not work at all >>on /etc/pve/ - instead, we use versions numbers to track changes (see >>/etc/pve/.version). ok great ! And how can we generate the config && reload network from here ? Can we call an external perl script ? ----- Mail original ----- De: "dietmar" <diet...@proxmox.com> À: "aderumier" <aderum...@odiso.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com>, "Stoiko Ivanov" <s.iva...@proxmox.com> Envoyé: Jeudi 4 Avril 2019 11:44:47 Objet: Re: [pve-devel] rfc : pve-network : idea to generate and reload config accross the nodes > >>So the idea is to detect network.cfg changes inside pmxcfs, and if we > >>detect changes > >>do a network reload. > >> > >>That way we can apply the config without an additional daemon - sounds > >>good. > > Sound good. (so we can do changes in network.cfg.tmp, still have the test > button(api call to each nodes), and apply change to network.cfg) > > > But how does it work ? who is currently listening for changes in pmxcfs ? > (through inotify?) This is low-level C-code inside pmxcfs (corosync). Please not that INotify does not work at all on /etc/pve/ - instead, we use versions numbers to track changes (see /etc/pve/.version). _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
