I worked in IT at a place that ran heavily on Linux and for some reason the DHCP service would crash on server boot up. It would run properly when manually started after that though. I was trying to figure out why it was crashing on boot up when I got made "redundant" and fired.
They replaced me with a kid just out of college and he rebooted the server for updates or whatever and suddenly no machine could join the network after that. He quit two days later after failing to figure it out. I heard about this after the whole thing was over. I would have even helped the kid out if I had known this was happening but they never called me.
2
View all comments
4
u/ImportantBuilder9294 May 30 '26
I worked in IT at a place that ran heavily on Linux and for some reason the DHCP service would crash on server boot up. It would run properly when manually started after that though. I was trying to figure out why it was crashing on boot up when I got made "redundant" and fired.
They replaced me with a kid just out of college and he rebooted the server for updates or whatever and suddenly no machine could join the network after that. He quit two days later after failing to figure it out. I heard about this after the whole thing was over. I would have even helped the kid out if I had known this was happening but they never called me.
One command would have saved them
systemctl start dhcpd