Perl 6 - the future is here, just unevenly distributed

IRC log for #crimsonfu, 2016-02-25

crimsonfu - sysadmins who code

| Channels | #crimsonfu index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
06:41 Azgarech joined #crimsonfu
14:10 pdurbin what do you call the "real" hostname? server123.foo.com is what the box knows itself as. what do you cal that? the rest of the world knows it as www.foo.com. would you call it the "machine name"?
15:23 bene www.foo.com is the website address
15:27 pdurbin I called server123.foo.com the "machine name" in an email I just sent. good enough I guess
15:28 bene server123 is the hostname
15:28 bene echo $HOSTNAME
15:28 bene grep HOSTNAME /etc/sysconfig/network
15:33 pdurbin yeah, I considered just calling server123.foo.com the hostname. or fqdn. but www.foo.com is a hostname and fqdn too. that's kind of my point. or question
15:49 bene www.foo.com is a service name/address/URI
15:49 bene but
15:49 bene *shrug*
15:50 pdurbin heh
15:50 bene i think it only matters if you're writing docs, and the more important thing is internal consistency i think
15:50 pdurbin yeah
16:35 dotplus it depends on context. If you're referring to www.foo.com as a hostname (the right hand side of an A/AAAA record), call it a hostname. There's no requirement that a host has but a single name. If you're referring to the http service and the vhost that serves requests to it, then make that clear in context.
16:37 dotplus 'inventory hostname' is a phrase that I sometimes use to refer to server123.foo.com that serves HTTP requests for www.foo.com, if the context is infrastructure/internal management.
16:45 pdurbin huh. inventory hostname
19:42 Azgarech joined #crimsonfu

| Channels | #crimsonfu index | Today | | Search | Google Search | Plain-Text | summary

crimsonfu - sysadmins who code