I need to disable the DHCP server on several SCO Openserver 6 boxes. I've managed it so far by logging in as root and running Scoadmin then blindly deleting all sorts of stuff in there and removing global settings etc. It doesn't matter as the servers are being replaced. I just need them to stop issuing addresses and DNS suffixes etc. There must be a more elegant way to do it than charging in there waving an axe (metaphorically speaking !).
Donald Trump needs kicking out of a helicopter
Offset "(Emp) - a little heavy on the hyperbole."
Comments
Offset "(Emp) - a little heavy on the hyperbole."
Offset "(Emp) - a little heavy on the hyperbole."
http://uw714doc.sco.com/en/man/html.1Mtcp/aasd.1Mtcp.html
"The Address Allocation Server daemon, aasd, allocates addresses to network services, such as DHCP, which need to assign temporary addresses. It manages the information about allocated addresses, such as the service requesting the address and for how long the address is reserved.
If the configuration file (/etc/inet/aasd.conf) exists, aasd starts automatically. The configuration file defines the address pools available for allocation along with server parameters."
The bit in bold would seem to suggest that if /etc/inet/aasd.conf doesn't exist, the AAS won't start. Try renaming it to aasd.conf.old, reboot and see what happens.
Admittedly, that's for a version of Unixware from 2004, but it's the closest I could find to something relevant.
How fast does your beard grow, Emp?
No pun intended !
Offset "(Emp) - a little heavy on the hyperbole."
Well, SCO would probably contend that I used it every day (I'm a Linux bod), but y'know...fuck SCO. Wankers.
Feedback
Feedback
I worked out myself how to discover the location of the shares and how to blow open the permissions, but the way SCO handles DHCP confused me. I stopped the AAS service and even deleted the DHCP scope, but the bloody thing was still handing out old DNS suffixes, which was playing hell with the clients. It wasn't until I also trashed the global settings that it finally died. I did however feel like a neanderthal clubbing it to death and I would prefer to learn how to shut it down gracefully !
Offset "(Emp) - a little heavy on the hyperbole."
Feedback
Another alternative would've been to fire up the new machines first, and then the old ones (thus having all the available DHCP requests already completed before the problematic servers started up).
If you need to kill it after a reboot then have a look if it gets started in an init.d script and remove that.