[00:02] <keithzg[m]> sarnold: Hmm, not that I can see. To be more specific, I'm trying to figure out what shell the user for `transmission-daemon` (which is "debian-transmission") uses; a script I'm trying to invoke fails if the shebang line just says `/bin/sh`, in a way that sure does seem like it's not bash!
[00:03] <sarnold> keithzg[m]: hmm. if the shebang line is busted then glibc (GLIBC!!) will also call /bin/sh on the file directly. seriously. :/
[00:04] <keithzg[m]> sarnold: Ah sorry to be clear it's indeed `#!/bin/sh`, I just meant it only specified /bin/sh rather than /bin/bash or such
[00:05] <sarnold> oh okay. so now the problem is, are they using dash or ask or bash or pdksh or ... you pretty much have to figure out which package owns /bin/sh, which varies from distro to distro
[00:06] <keithzg[m]> Well, the distro in question is one I think most of us here in this channel are quite familiar with ;)
[00:06] <keithzg[m]> Specifically, 18.04
[06:11] <lordievader> Good morning
[11:18]  * zeph1ro waves @rbasak & @cpaelzer
[11:23] <rbasak> o/
[13:39] <Odd_Bloke> keithzg[m]: /bin/sh will be dash on Ubuntu.
[15:41] <set_> How can I simplify my https://blah-blah.com domain to show when I type blah-blah.com or another form of that domain?
[15:41] <set_> ...
[15:41] <set_> For instance, it is like I have to type the https://blah-blah.com exactly or I receive errors (all sorts).
[15:44] <Odd_Bloke> set_: Can you give an example of something that works as you're expecting, and something that doesn't work as you're expecting?
[15:45] <set_> sure. I type blah-blah.com and nothing happens except for the browser stating no server found.
[15:45] <set_> I type https://www.blah-blah.com and it works fine.
[15:45] <Odd_Bloke> set_: I assume you aren't talking specifically about blah-blah.com?
[15:45] <set_> For lazy typists, the https://www. is an extra bunch of efforts that might not be in their ideas.
[15:45] <set_> Right.
[15:45] <set_> I have a site.
[15:46] <Odd_Bloke> OK, so that's going to make it harder to help you, but it sounds like you have a DNS problem.
[15:46] <set_> Oh.
[15:46] <set_> Okay.
[15:46] <tomreyn> what you want there is either a HSTS header or the webserver listeining on the HTTP (80) port, sending a redirection to connection browsers
[15:46] <Odd_Bloke> tomreyn: That's a different issue, I think.  This is about www.example.com vs example.com
[15:47] <tomreyn> yes, but "I have to type the https://blah-blah.com exactly or I receive errors" sounded like the www. is just a side issue.
[15:47] <set_> Okay. I have two files w/ an apache2 server in /etc/apache2/sites-available/.
[15:47] <set_> One is *:80 and another w/ *:443.
[15:48] <set_> I have my certs. w/ the 443 file in /sites-available.
[15:48] <set_> I am reviewing my files now to look things over.
[15:49] <Odd_Bloke> set_: What does `nslookup blah-blah.com` output?  (Is NXDOMAIN in the output?)
[15:49] <set_> Please hold. I will check.
[15:51] <set_> It shows a Server, Address, and states non-authoritative answer: *** Can't find blah-blah.com: No answer.
[15:51] <set_> ...
[15:52] <tomreyn> so Odd_Bloke guessed right
[15:52]  * tomreyn bows
[15:53] <set_> Ooh la la!
[15:54] <tomreyn> set_: so who manages your domains' authoritative DNS?
[15:54] <set_> Oh. I used Linode for it but it is usually google.
[15:54] <tomreyn> well i don't need to know, but you'll need to have them add another record for just blah-blah.com pointing to your webserver's IP address
[15:55] <set_> Oh. That sounds easy enough.
[15:55] <set_> Off to test it.
[15:55] <set_> !
[15:56] <tomreyn> set_: and commonly you'll have the www record replaced by a cname pointing to blah-blah.com
[15:57] <set_> That is what I did.
[15:57] <set_> Let me check.
[15:57] <tomreyn> see the output of    nslookup www.megaglest.org    vs    nslookup megaglest.org
[15:57] <tomreyn> and compare to your domain
[15:57] <set_> When you are right, you are right. That worked like a charm.
[15:58] <tomreyn> www.megaglest.org is a CNAME to megaglest.org, which has an A record pointing to an IPv4 server address.
[15:58] <set_> Okay.
[15:58] <set_> So, in my .conf files, I should not use an alias?
[15:59] <tomreyn> your conf file should have a serveralias with the www in it
[15:59] <set_> Aw! Okay.
[15:59] <tomreyn> and an ssl certificate covering both the plain domain and the www subdomain, too
[15:59] <set_> Oh!
[15:59] <set_> Okay. That is what I have not tried yet.
[15:59] <set_> subdomain...This is what I did not want to call it b/c I was not sure.
[16:00] <tomreyn> it's not the greatest term
[16:00] <set_> It is one of those things, I guess.
[16:01] <tomreyn> you can say 2ns level domain name (blah-blah.com, one dot in there seperating two words) vs 3rd level domain name (www.blah-blah.com, two dots in there seperating three words)
[16:01] <tomreyn> *2nd
[16:01] <set_> Oh. Okay.
[16:01] <set_> I got it.
[16:03] <tomreyn> the :80 virtualhost should only have a redirection to httpS in there
[16:03] <set_> Oh.
[16:03] <set_> I do not have that yet.
[16:03] <set_> I will have to figure that one out.
[16:04] <tomreyn> and, actually before that, you should decide whether you want to have website visitors end up on the www or the non www url.
[16:04] <set_> Oh. I know nothing about that idea.
[16:04] <set_> I just know...I want to set up an okay site for maybe looking for work.
[16:05] <tomreyn> you don't want them to just reach one or the other and get your website there, one of those should redirect to the other, and the :80 virtualhost should redirecto to httpS on the domain you have chosen
[16:05] <set_> Right.
[16:05] <leftyfb> Can /etc/hosts be populated with your FQDN from DHCP? I can't seem to get it to do so. I'm running isc-dhcp-server and have the option domain-name "my.domain"; set properly and it gets used when writing to /etc/resolv.conf for search, but not /etc/hosts
[16:06] <tomreyn> i think /etc/hosts is specifically meant to be static
[16:07] <leftyfb> tomreyn: so then hostname -d will never work across multiple networks
[16:07] <leftyfb> since the only way that works is to have /etc/hosts populated with your fqdn
[16:07] <set_> I just got what I did. I was backwards on my server name and alias. Oops!
[16:09] <tomreyn> leftyfb: hmm i'm not actually sure, i guess you're right
[16:09] <leftyfb> boo
[16:09] <leftyfb> tomreyn: I only ever ask the tough questions :)
[16:10] <tomreyn> ;-)
[16:11] <tomreyn> set_: well you can have blah-blah.com be a CNAME to www.blah-blah.com, but that's no longer common (thankfully) nowadays.
[16:11] <set_> Oh.
[16:11] <set_> Okay.
[16:11] <set_> As you can tell, I am new in this field of Ubuntu_servers.
[16:12] <set_> I just started from an nginx book i picked up. I am using apache2 instead. Yea boy!
[16:12] <tomreyn> being new to things happens to the best of us at least once.
[16:12] <set_> Right-o. I guess I need a good site for redirection. I should start looking.
[16:12] <set_> I found some but not from ubuntu.com yet.
[16:13] <tomreyn> personally i'd recommend startng with apache httpd then move to nginx
[16:13] <tomreyn> nginx httpd that is
[16:13] <set_> That is what i am doing. My commands in nginx did not work. I had to erase the entire set up.
[16:13] <set_> Oh. httpd.
[16:13] <set_> got it.
[16:14] <tomreyn> because nginx tried to be all-the-services-you-might-ever-need-in-one-piece-of-software
[16:14] <tomreyn> but most people really just want to use the webserver
[16:14]  * teward saw nginx mentioned
[16:15] <tomreyn> teward saw right
[16:15] <teward> though i'm half-distracted at the moment (Eoan dev stuff)
[16:15] <tomreyn> get fully distracted again
[16:16] <tomreyn> back to work ;-P
[16:16] <teward> tomreyn: WORK:BLOCKED (waitingOn: vorlon)
[16:16] <tomreyn> oh useful
[16:16] <set_> Thank you...
[16:16] <teward> hence half-distracted :P
[16:17] <tomreyn> set_: so if you have nginx questions, bring them up, since teward wants to be half entertained
[16:18] <teward> or i'm just going to go yell at the Lubuntu folks again which is less than productive :P
[16:18] <set_> Oh.
[16:18] <teward> i'm also the nginx package maintainer(ish) here in Ubuntu :P
[16:18] <set_> I will have to set things up again. I erased all my .conf files already.
[16:18] <set_> Oh. Okay.
[16:19] <set_> nice to meet you teward.
[16:20] <set_> I am actually receiving two, separate sites for blah-blah.com and https://www.blah-blah.com.
[16:20] <set_> Odd days.
[16:20] <set_> dang it. brb.
[16:34] <set_> Okay.
[16:35] <set_> I am looking on httpd.apache2.com and I found a redirect directive.
[16:35] <set_> I am getting close.
[16:36] <set_> .com = .org
[16:36] <set_> Oops.
[16:44] <set_> Would I use two files for :80 and :443 or would I just use one w/ multiple VirtualHost directives?
[16:46] <teward> you could do either, but if you're using Apache you may want to keep the http and https ones (80 and 443 respectively) as their own site directive files that you can activate/deactivate independently of each other
[16:50] <set_> Okay.
[16:50] <set_> Good idea.
[16:52] <set_> Well, the redirect works now. This is good news.
[16:52] <set_> Things seem much better when it works out.
[23:32] <Nizumzen> sorry to ask an off-topic question but what is the best domain registrar these days? I've been using Namecheap for years but I'm wondering if there is a better one to transfer to?
[23:33] <sarnold> I've been happy enough with gandi but namecheap comes up often in these discussions
[23:35] <tumbleweed> cloudflare registrar these days, too
[23:35] <teward> namecheap for SSL, Gandi for registration, but I"m biased because of the discounts I get on my costs thanks to Ubuntu Membership from a while ago xD
[23:35] <teward> Cloudflare Registrar is there too though as an option
[23:35] <teward> (but I haven't used them)
[23:35] <teward> (though I use Cloudflare for DNS xD)
[23:37]  * tomreyn likes inwx.com, joker.com, njalla.org
[23:38] <tomreyn> and freenom.com if it has to be free.
[23:40] <Nizumzen> thanks for the suggestions - I'll check them out