Apparently there was also (and may still be somewhere) a command line "crypt" that I could have "front-ended" for my needs, but it doesn't exist on my system. As there really isn't much to this, I just went ahead and wrote what I needed.
- Another SCO 5.0.7 crash tests my memory - it was taxing, but we got through it. A decade ago or more that would have been something I could fix while half awake, but now my memory of SCO Unix has truly faded. -
- Early SCO Unix had no DHCP capability (it did have DHCP server). That perhaps was somewhat reasonable; these machines were servers and could be expected to have a static IP address. However, as DHCP can do much more than simply provide an IP address, having DHCP would have been advantageous at times. -
- Aside from transferring user accounts, printers, and so on, my work was just to convert Vsifax scripts to Hylafax. Those scripts were called by the application program to do such things as fax a Purchase Order to a vendor. The programming is simple enough: you find and extract the fax number and pass that all off to Hylafax. For purposes of logging and error control, we also wanted to identify the vendor name, which required adding that name to the logs that Hylafax keeps or maintaining a separate index of names to faxes queued. -
- I'm doing another SCO to Linux conversion and this one used Vsifax. That's hardly a show stopper, but this customer wanted to use Centos and Vsifax says they don't currently support using Centos. So we tried Hylafax. -
- I have a server that reboots itself every morning and sets the time to 12:00 CT, which ntp then corrects. I've checked the crontab and at jobs. The syslog and messages files have no logging other than the standard system start up messages. -