On 5/2/07, Thomas Kern <[EMAIL PROTECTED]> wrote:
You still have to write some rexx/xedit code to issue the commands to read/write the tags and data, just like for using the names file. One advantage to using DIRMAINT as your database is that it is already a shareable database not a private one.
The thing that I like about such an approach is that you have one place less to keep track of, which can make a big difference. If you just need to keep track of the host name or IP address, it would work extremely well this way. And at least one of the information items is up-to-date because it is actually *used* from there in the system. But it tends to get messy when you grow beyond the initial design (like having multi-homed servers). Most "convenient" place to hold the data is where you can keep it up-to-date or better something does that for you. If you manage a DNS server that is authorative for some domains, you can make cname's etc to document your configuration, and actually use them there and have the need to keep it up-to-date. In a former life we did the DNS updates through some line-mode DNS-update tools (instead of hacking the zone files) so you have a proper audit trail and can add extra checks as well. When a separate spreadsheet / document / shoe carton with a copy of the configuration items is not up-to-date, the punishment for that is often not immediate enough so that updates are often postponed. But no doubt you all are way more disciplined than I am :-) Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
