- Roundtable - muug.ca

muug.ca server outage
by Trevor Cordes 11 Sep '24

11 Sep '24

The muug.ca mirror and mailing list server will be down a for several hours (and possibly days) for a planned update. The mailing lists will be down even longer (a day to a week).

1 0

Reminder: MUUG Meeting, Tonight, Sept 3, 7:30pm (In-person/Hybrid Meeting) -- lighttpd & Sublime Text
by Gilbert Detillieux 03 Sep '24

03 Sep '24

A reminder that the MUUG meeting will be this evening, both in person and online... The Manitoba UNIX User Group (MUUG) will be holding its next monthly meeting IN PERSON, on Tuesday, September 3rd, at 7:30pm. Yes, that's the FIRST Tuesday of the month... Fly light!, plus Sublime Text Kevin McGregor will provide a gentle introduction to the lighttpd web server. "lighttpd (pronounced lighty) is a secure, fast, compliant, and very flexible web server that has been optimized for high-performance environments. lighttpd uses memory and CPU efficiently and has lower resource use than other popular web servers. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and much more) make lighttpd the perfect web server for all systems, small and large." For our mini-presentation of a "desktop app," Brad Vokey will do a quick demonstration of his favourite GUI text editor: Sublime Text - "Text Editing Done Right." Sublime Text is a fast, mature, light weight, beautiful, customizable, expandable, cross-platform, "shareware" text editor. Brad has previously written about Sublime Text in the MUUG 2021-06 newsletter (page 5), and he will now give us a quick intro into some of it's features. Where to find the Meeting: Fortress Software Inc., 350 Keewatin St -- Unit #2 We have a new in-person meeting location now! Brad Vokey has graciously let us use his work office for our next in-person meeting. The meeting room will be open by 7:00 pm, with the actual meeting starting at 7:30 pm. If driving, enter the lot using the most north east entrance and drive around to the south west corner of the building (see route in map detail on poster linked below). You can use any of the free, ample, and safe parking spots that say "reserved" in front of units #1 through #4 before entering unit #2. Bus stops #30814 and #30880 (route 77) are only 150 meters away. The last bus leaves for Polo Park at 10:15 pm and for Garden City at 10:31 pm. Logan Ave. bus routes #19, #26, and #27 are a 600 meter (8 minute) walk to the south. For those unable or preferring not to attend in person, the meeting will also be available online, using BBB as usual. Stay tuned to our muug.ca home page for the official URL, which will be made available about a half hour before the meeting starts. (Reload the page if you don't see the link, or if there are issues with connecting.) The group now holds its meetings at 7:30pm on the *first* Tuesday of every month from September to June. (There are no meetings in July and August.) Meetings are open to the general public; you don't have to be a MUUG member to attend. For more information about MUUG, and its monthly meetings, check out their web server: https://muug.ca/ Help us promote this month's meeting, by putting this poster up on your workplace bulletin board or other suitable public message board, or linking to it on social media: https://muug.ca/meetings/MUUGmeeting.pdf -- Gilbert E. Detillieux E-mail: <gedetil(a)muug.ca> Manitoba UNIX User Group Web: http://muug.ca/

1 0

Cell phone signal booster?
by Kevin McGregor 02 Sep '24

02 Sep '24

Does anyone have one of these? Do they work in areas with poor reception? I'm going to be out in the boonies and I'm worried I won't get calls. BellMTS, in Spruce Woods Provincial Park if it matters.

4 7

Android virus scan
by Rob Dyck 29 Aug '24

29 Aug '24

4 11

MUUG Meeting, Tuesday, Sept 3, 7:30pm (In-person/Hybrid Meeting) -- lighttpd & Sublime Text
by Gilbert Detillieux 28 Aug '24

28 Aug '24

The Manitoba UNIX User Group (MUUG) will be holding its next monthly meeting IN PERSON, on Tuesday, September 3rd, at 7:30pm. Yes, that's the FIRST Tuesday of the month... Fly light!, plus Sublime Text Kevin McGregor will provide a gentle introduction to the lighttpd web server. "lighttpd (pronounced lighty) is a secure, fast, compliant, and very flexible web server that has been optimized for high-performance environments. lighttpd uses memory and CPU efficiently and has lower resource use than other popular web servers. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and much more) make lighttpd the perfect web server for all systems, small and large." For our mini-presentation of a "desktop app," Brad Vokey will do a quick demonstration of his favourite GUI text editor: Sublime Text - "Text Editing Done Right." Sublime Text is a fast, mature, light weight, beautiful, customizable, expandable, cross-platform, "shareware" text editor. Brad has previously written about Sublime Text in the MUUG 2021-06 newsletter (page 5), and he will now give us a quick intro into some of it's features. Where to find the Meeting: Fortress Software Inc., 350 Keewatin St -- Unit #2 We have a new in-person meeting location now! Brad Vokey has graciously let us use his work office for our next in-person meeting. The meeting room will be open by 7:00 pm, with the actual meeting starting at 7:30 pm. If driving, enter the lot using the most north east entrance and drive around to the south west corner of the building (see route in map detail on poster linked below). You can use any of the free, ample, and safe parking spots that say "reserved" in front of units #1 through #4 before entering unit #2. Bus stops #30814 and #30880 (route 77) are only 150 meters away. The last bus leaves for Polo Park at 10:15 pm and for Garden City at 10:31 pm. Logan Ave. bus routes #19, #26, and #27 are a 600 meter (8 minute) walk to the south. For those unable or preferring not to attend in person, the meeting will also be available online, using BBB as usual. Stay tuned to our muug.ca home page for the official URL, which will be made available about a half hour before the meeting starts. (Reload the page if you don't see the link, or if there are issues with connecting.) The group now holds its meetings at 7:30pm on the *first* Tuesday of every month from September to June. (There are no meetings in July and August.) Meetings are open to the general public; you don't have to be a MUUG member to attend. For more information about MUUG, and its monthly meetings, check out their web server: https://muug.ca/ Help us promote this month's meeting, by putting this poster up on your workplace bulletin board or other suitable public message board, or linking to it on social media: https://muug.ca/meetings/MUUGmeeting.pdf -- Gilbert E. Detillieux E-mail: <gedetil(a)muug.ca> Manitoba UNIX User Group Web: http://muug.ca/

2 1

/tmp longevity
by Kevin McGregor 15 Aug '24

15 Aug '24

Back in the day(?) I thought that the entire contents of /tmp would be wiped on every reboot. It sorta seems like it for Ubuntu 18.04, but with 22.04 that doesn't seem to be the case at all, with conf files in /etc/tmpfiles.d and elsewhere which describe what gets deleted. Can anyone shed any light on this, at least for Debian/Ubuntu? When did this change?

3 2

Beautiful shell script example
by Adam Thompson 30 Jul '24

30 Jul '24

https://hackaday.com/2024/07/29/getting-linux-process-list-without-forking-… I wish I could hire the author of the script. -Adam Get Outlook for Android<https://aka.ms/AAb9ysg>

1 0

Subdomain wildcard in Bind-style DNS editing
by Hartmut W Sager 24 Jul '24

24 Jul '24

I have a question about subdomain wildcards in Bind-style DNS editing, so that I can more conveniently edit DNS zone files to implement Fastmail's support of MX records specifying "*.mydomain.com." for e-mail at subdomains. (Yes, Fastmail's documentation states their support for this.) Now, in Bind-style DNS, we have valid short notations for full FQDN in the name field (the left side) as follows: "@" = "mydomain.com." "abc" = "abc.mydomain.com." So my question is, might the following also be valid? "*" = "*.mydomain.com." "*.@" = "*.mydomain.com." Hartmut

3 2

RHEL latest package?
by Trevor Cordes 20 Jul '24

20 Jul '24

I finally gained access to the documentation for RHEL for a dedicated-hosting RHEL server I work on. But I find it hard to figure out where to go in there to find much of anything. And google doesn't seem to index what it is I need, maybe because of the paywall? I'm trying to figure out 2 things: 1. How can I tell what is the latest rpm/version RH has put out for httpd? I'm talking stock RHEL-supplied, not IUS/EPEL or whatever 3rd party. I know in Fedora this would be simple with bodhi/koji and/or simple rpmfind. 2. How can I tell if my RHEL box is setup to receive updates? Dnf works to install packages, but no updates seem to be coming across? I'm a bit worried because of the recent not-so-great apache/httpd bugs. I know RH has all this subscription stuff I normally don't have to mess with with Fedora, and I like to think the dedicated hoster set this all up properly, but I'm not sure how to tell. Thanks!

2 1

dialog(1) shell fd acrobatics question
by Adam Thompson 08 Jul '24

08 Jul '24

I’m trying to debug a shell script that uses dialog(1), which has the unfortunate habit of overwriting the debug output I wanted to see. After quite some time banging my head against the wall, I grabbed the source to dialog to look at their examples. Their examples follow a pattern I have NOT been following; I’m now looking at this trying to understand WTF it does: 1 exec 3>&1 2 returntext=`$DIALOG --title "RANGE BOX" --rangebox "Please set the volume..." 0 60 0 123 5 2>&1 1>&3` 3 returncode=$? 4 exec 3>&- so… ok. Line 1 duplicates FD 1 (stdout) into FD 3. That’s usually so we can mess with FD 1 later on and still have a handle to stdout. Good so far. Line 2 runs /usr/bin/dialog in a subshell, the options to dialog(1) are irrelevant here. I’m looking at the redirects. “2>&1” duplicates FD 1 into FD 2, effectively throwing away the handle to the inherited /dev/stderr and forcing stderr output onto stdout. That’s a good thing because dialog(1) reports its results onto stderr by default to avoid messing with curses(3) output. “1>&3” however, throws away stdout (FD 1), replacing it with FD 3 which is… already a copy of FD 1 ??? Line 3 is obvious. Line 4 closes FD 3. Not sure that we need to bother, but OK, cleaning up behind ourselves is usually a good thing. I get the need for swapping stdin/stderr, as dialog(1) – well, really curses(3) - uses stdout to paint the screen, so dialog(1) spits its results out on stderr to avoid conflicting. If we’re in a subshell trying to capture that output, we need to grab it just as dialog(1) exits – and $() assignment only captures stdout. But what’s the point of having FD 3 in this setup, if all we do is assign it to stdin inside the subshell and then forget about it? Can anyone see what I’m missing here? -Adam

3 3