CronJobs run on virtual machines house in specific NFS servers. All files are also house on specific NFS servers. (which will be documented via attributes). The machine NFS servers can just be recorded as a core dictionary.
When writing a cronjob node with a wrapper script, or injecting an Edge between any nodes, we should traverse database relationships up to the parent crontab machine to identify where there is a discrepancy between where the top level CronTab machine is house, and the descendant node being interacted with.
if the discrepancy is notice, this automatically writes an entry to the NodeMetaData table or EdgeMetaData table highlighting the discrepancy. Thus populating our database will automatically fill this information as well.
CronJobs run on virtual machines house in specific NFS servers. All files are also house on specific NFS servers. (which will be documented via attributes). The machine NFS servers can just be recorded as a core dictionary.
When writing a cronjob node with a wrapper script, or injecting an Edge between any nodes, we should traverse database relationships up to the parent crontab machine to identify where there is a discrepancy between where the top level CronTab machine is house, and the descendant node being interacted with.
if the discrepancy is notice, this automatically writes an entry to the NodeMetaData table or EdgeMetaData table highlighting the discrepancy. Thus populating our database will automatically fill this information as well.