The current DIRMAINT has special user-defined fields called TAGS. They can be
created, modified, deleted by standard DIRMAINT commands, not just
get|edit|replace.
<snipped from DIRMAINT DEFINESTAG command>
Use the DEFINESTAG operand of the DIRMAINT command to manipulate user defined
tagged comments. An installation can define local tags that can be stored in
the CP directory and manipulated by DirMaint. This may be useful for
information normally placed into comments, such as department information.
This command creates the required definitions within the DIRMAINT machine. It
is not used to assign data to a local tag, it is only used to create and
manipulate a local tag.
<end-snip>
So the example directory entry could look like this:
USER LIONELVM ...
... other stuff ...
*ipaddr:1.2.3.4
*hostname:lionelvm
*macaddr:0040052142C7
... more stuff ...
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.
/Tom Kern
--- Rick Troth <[EMAIL PROTECTED]> wrote:
> The Cat Herder will kill me for saying this:
> You might want to overload your CP Directory. (Here I do not mean
> "overload" in the negative sense.) I mean, define some of your own
> sacred comments in the CP Dir source much like VM:Secure does. Works!
>
> Consider a NAMES file. And if you choose a NAMES file
> you could connect it to the CP Dir source with a "sacred comment".
>
> :nick.LIONELVM :userid.LIONELVM
> :ipaddr.1.2.3.4 :hostname.lionelvm :macaddr.0040052142C7
>
> would translate to CP Dir comment statements
>
> USER LIONELVM ...
> ... other stuff ...
> *:ipaddr.1.2.3.4
> *:hostname.lionelvm
> *:macaddr.0040052142C7
> ... more stuff ...
>
> Userid is clearly implied by being part of a given CP Dir entry.
> And nick is not strictly needed. Heck, any line starting with "*:"
> could be taken as "NAMES data" so the two lines could be merged as
>
> *:ipaddr.1.2.3.4 :hostname.lionelvm :macaddr.0040052142C7
>
> ... as long as the whole thing fits in the 72 columns allowed for
> CP Dir source. When you extract those statements to a NAMES file
> just strip off the leading asterisk and ... voi-la!
>
> So then comes DNS and DHCP. No problem! Whether NAMES data
> or some other form, use Pipelines to convert that into the
> plain text required by these critters.
>
> lionelvm IN A 1.2.3.4
>
> (for DNS)
>
> host lionelvm {
> hardware ethernet 00:40:05:21:42:C7;
> fixed-address lionelvm.kp.org;
> }
>
> (for DHCP)
>
> -- R;
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
----------------------------------------------------------------------
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
