Custom Query (98 matches)

The host OS on pc5.utah.geniracks.net contains the standard DNS resolution client tools:

vhost1,[~],10:01(0)$ ls -1 /usr/bin/{host,dig,nslookup}
/usr/bin/dig*
/usr/bin/host*
/usr/bin/nslookup*

However, these tools seem to be missing from inside my container, virt1.ecgtest2:

[chaos@virt1 ~]$ ls -1 /usr/bin/{host,dig,nslookup}
ls: cannot access /usr/bin/host: No such file or directory
ls: cannot access /usr/bin/dig: No such file or directory
ls: cannot access /usr/bin/nslookup: No such file or directory

[chaos@virt1 ~]$ type host
bash: type: host: not found
[chaos@virt1 ~]$ type dig
bash: type: dig: not found
[chaos@virt1 ~]$ type nslookup
bash: type: nslookup: not found

This seems unexpected. I would think experimenters might want to be able to do DNS lookups, e.g. to download tools on the control network.

There should be a plan or checklist for creating accounts on a rack for a new site admin.

Chaos (chaos) and Josh (jbs) should have accounts on flowvisor.utah.geniracks.net for initial rack testing at Utah.

[Note: when the BBN rack arrives, we will no longer be doing site admin testing at Utah, at which time this ticket can be closed as invalid.]