DHCPD conf file change of default directory after Gitsync
-
Hello,
I'm on a Beta 2.0 (28/10 snapshot)
I've made a gitsync this morning.
Aftrer reboot, dhcpd does not start…Looking at logs :
php: /status_services.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf rl0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server V3.0.7 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Can't open /etc/dhcpd.conf: No such file or directory'
So I had to cp /var/dhcpd/etc/dhcpd.conf to /etc/dhcpd.conf to have dhcpd working.
My question : If I make a change with the webgui, will it now write to /etc/dhcpd.conf or in the old file /var/dhcpd/etc/dhcpd.conf
Of course you can tell me try it… ;D
But I wanted to warn you about this little problem. ;) -
You need a new dhcpd binary.
-
By the way, if you want to go back to the version of the code that came with the build you have installed, you can use the special "build_commit" branch name in gitsync and it will roll back to that version.
There is always a risk when using gitsync that you may get some changes applied that require updates to one or more of the binaries for it to work. If you want to get a better idea of when gitsync might break things, keep an eye out for recent updates on the pfSense Tools repository.
https://rcs.pfsense.org/projects/pfsense-tools
-
Hi,
@ermal:
You need a new dhcpd binary.
As simple as```
pkg -r add dhcpcd-3.2.3.tbz@Efonne: > By the way, if you want to go back to the version of the code that came with the build you have installed, you can use the special "build_commit" branch name in gitsync and it will roll back to that version. > > There is always a risk when using gitsync that you may get some changes applied that require updates to one or more of the binaries for it to work. If you want to get a better idea of when gitsync might break things, keep an eye out for recent updates on the pfSense Tools repository. > > https://rcs.pfsense.org/projects/pfsense-tools Yes, there is always a risk, I am aware. Thank you for the link, I would watch this before next upgrades. For now my pfSense is fortunately not broken. There was just the dhcp server which stuck a little … it's time to install a second dhcp on my network, for next time... ;) -
Hi,
@Efonne:By the way, if you want to go back to the version of the code that came with the build you have installed, you can use the special "build_commit" branch name in gitsync and it will roll back to that version.
For more information how does it work exactly ?
-
@lol:
Hi,
@Efonne:By the way, if you want to go back to the version of the code that came with the build you have installed, you can use the special "build_commit" branch name in gitsync and it will roll back to that version.
For more information how does it work exactly ?
Ok, sorry. I found…
pfSsh.php playback gitsync Starting the pfSense shell system.............. Current repository is http://gitweb.pfsense.org/pfsense/mainline.git Please select which branch you would like to sync against: master 2.0 development branch RELENG_1_2 1.2* release branch build_commit The commit originally used to build the image Or alternatively you may enter a custom RCS branch URL (HTTP). > build_commit etc...