●● IRC: #boycottnovell-social @ FreeNode: Thursday, December 31, 2020 ●●
● Dec 31
[04:47] Techrights-sec Very few rC3 talks online yet. And those have had technical failures.
[04:47] Techrights-sec One on climate suggests a tipping point has been crossed already
[04:47] Techrights-sec in regards to ice loss and sea level rise.
[04:47] Techrights-sec At least they have the moderators presenting the questions rather
[04:47] Techrights-sec than directly from participants.
● Dec 31
[05:42] *viera (~viera@2602:fd37:1::84) has joined #boycottnovell-social
● Dec 31
[06:51] *viera has quit (Remote host closed the connection)
[06:52] *viera (~viera@2602:fd37:1::84) has joined #boycottnovell-social
[06:55] *viera has quit (Remote host closed the connection)
● Dec 31
[08:35] schestowitz Hi, on xmas/NYE 2018 I requested DNS changes to tuxmachines.org
[08:35] schestowitz That domain has been on my account for a while and again, when things are calm, we need to switch to another IP and DC. The new IP address for tuxmachines.org is 23.161.112.115
[08:35] schestowitz The current:
[08:35] schestowitz NS5.CATALYST2.NET
[08:35] schestowitz 84.18.207.222
[08:35] schestowitz NS6.CATALYST2.NET
[08:35] schestowitz 185.28.164.100
[08:35] schestowitz 84.18.207.222 will be shut down soon, so please change to 23.161.112.115
[08:35] schestowitz Can you update ASAP? We want to keep the old and new in sync while switching over
[08:35] schestowitz Last time you asked me for verification details
[08:35] schestowitz My postcode is xxxxx (might still be an older one on file, with xxxx).
[08:35] schestowitz I can phone you if that speeds things up.
● Dec 31
[09:12] schestowitz at some stage various scripts will need to be updated to keep up with IP changes, later there will be more containers with alpine
[09:13] schestowitz at the moment I am checking logs for httpd on the new tuxmachines server to see if some have had their DNS servers updated already
[09:13] schestowitz I need help. I cannot figure out why the du size for the most important dir, /var/www , is not the same on old and new servers
[09:14] schestowitz and also the length of find, though I assume based on some tests that the changes in underlying filesystems cause the difference
[09:22] Techrights-sec diff <(ssh old "ls -R /var/www/ | sort") <(ssh new "ls -R /var/www/ | sort")
[09:22] schestowitz OK, let's start with this
[09:22] schestowitz 1. can you ssh both servers OK? The new ones?
[09:23] schestowitz 2. I want to do a sanity check (that "dirty" and "offensive" term) to make sure we leave no files 'behind'. The rest we can repair in place, I just don't want to lose files from the past 17 years
[09:25] schestowitz 3. after the sanity check we need to stress-test the thing, to make sure all sorts of things work. Later on (4-x) will be steps like alpine, adding ssl... we'll have TBs of disk space
[09:25] Techrights-sec What is the current IPv4 number of the new TR and TM?
[09:25] schestowitz 23.161.112.115 and 23.161.112.116
[09:26] schestowitz 32 cores, no ME :-)
[09:29] Techrights-sec Different ssh_host_rsa_key?
[09:30] schestowitz use password, then change your key if needed?
[09:31] Techrights-sec Not my key, /etc/ssh/ssh_host_rsa_key ?
[09:31] Techrights-sec On the new server.
[09:31] Techrights-sec Can you run ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub and post the fingerprint?
[09:38] schestowitz good news. ls -R /var/www/ | sort | wc worked like a charm
[09:38] schestowitz and it shows identical number of files across old and new
[09:39] schestowitz I just assume the files too are the same, or I'll just check character count
[09:39] schestowitz in techrights there are some cache files building up, so crude file count might yield different results
[09:41] schestowitz As I expected, the wordpress post for today's IRC was added shorted after we rsynced the DB, so will manually copy that across to the new DC
[09:41] schestowitz I will do this now, carefully
[09:42] Techrights-sec Ok. 115 matches and can log in. Takes a bit to translate the checksum format
[09:42] Techrights-sec for 116?
[09:45] schestowitz : --- )))) /dev/vda3 1052255236 99572080 952683156 10% /
[09:46] schestowitz doing some sanity checks on the filesystem of TR now, could not find issues on TM
[09:47] Techrights-sec ok
[09:47] Techrights-sec Ok can log into the new TM too
[09:47] schestowitz 116 is new TR
[09:48] schestowitz On my ISP TM is now the new server... the DNS entry is updated here
[09:49] schestowitz That's you ->> TR: xxxx pts/6 2020-12-31 09:46
[09:49] schestowitz irc-archives]$ ls -la | wc
[09:49] schestowitz 2990 26903 242527
[09:50] schestowitz 8 new files per day, plus additional one annually for the tuxmachines channel
[09:50] Techrights-sec I seem to still have the old DNS entries
[09:50] schestowitz I checked the IRC bot, it gives 404 if I feed it the new test post on the "other side" (new machine)
[09:51] schestowitz I instructed rianne not to post until late in the day, otherwise people in places like chile will just get frustrated with error pages (wrong server reached)
[09:52] schestowitz Migrating TuxMachines to a Bigger Server
[09:52] schestowitz We are in the process of moving the TuxMachines Web site to a better server with more capacity and better hardware. There may be temporarily odd behaviour on the site (if data is accessed which is out of date).
[09:52] Techrights-sec It's too late now but was the TTL reduced before the changeover
[09:52] Techrights-sec and then turned back to normal TTL?
[09:53] schestowitz I have not checked, why?
[09:53] schestowitz What I do know is that with more CPU cores TR >ought< to load up faster, for all parts of the side
[09:53] schestowitz What I do know is that with more CPU cores TR >ought< to load up faster, for all parts of the site
[09:56] schestowitz it seems like adding the 'new' IRC blog post to the new server would be easier to do after the DNS switchover, as WordPress has rather strict domain-based restrictions and I don't want to mess things up
[09:58] schestowitz With my ISP now pointing at the right place I am stress testing and stuff at TM
[09:59] schestowitz You can force feed the new IP address in places of techrights.org for various URLs and CMSs part to see if you can spot issue. Then we can update DNS and in case there are issues we can roll back.
● Dec 31
[10:01] schestowitz LOL, my ISP's DNS is not consistent or in 'flux'... will map the requests to different IPs at different times ;)
[10:01] Techrights-sec Probably some round-robin DNS and one of them got queried while the old
[10:01] Techrights-sec IPv4 number was in effect.
[10:02] schestowitz Yes, that's what I assumed. That makes proper testing a tad premature at this level.
[10:02] schestowitz I did:
[10:02] schestowitz 1) check that static files are OK
[10:02] schestowitz 2) mine types
[10:02] schestowitz 3) mailing lists archives
[10:02] schestowitz 4)
[10:02] schestowitz wiki
[10:02] schestowitz 5) drupal: SOON
[10:03] schestowitz 6) wordpress is slightly out of date, I will copy across the IRC post later on, it's just a 1-minute copy-paste job
[10:04] schestowitz I am going to crude file-count now
[10:04] schestowitz kaniini did rsync twice over just in case, but I want to examine for confidence
[10:06] Techrights-sec Usually one should stop the VM completely for final sync
[10:06] schestowitz I think the only files changes 'in vivo' are wordpress cache files
[10:09] schestowitz ok, thanks for the help
[10:09] Techrights-sec xxxxx
[10:11] schestowitz report to self/record:
[10:12] schestowitz 1) files across /root identical (without doing checksums, just names)
[10:13] schestowitz 2) almost 170,000 files in /home and due to caching one is expected to be a tad higher than the other
[10:14] schestowitz nevertheless, at the moment number of files are the same, and char length/count the same also
[10:14] schestowitz ls -R /home | sort | wc
[10:14] schestowitz 168247 162554 5868471
[10:14] schestowitz 3) no issues encountered with database/settings, checking video for mime type issues (we had such issues 7 years ago when we had to change configs manually in centos)
[10:18] schestowitz 4) permissions copied across correctly, just checked SLAPPed URLs are blocked (not mine, patent trolltracker's, he asked me to hide his archives posts due to the lawsuit Ray Niro filed)
[10:22] Techrights-sec yes, the backups also don;t get trolltracker
[10:22] Techrights-sec afaik
[10:22] schestowitz only about 4 pages, IIRC, the ones that cause him trouble if accessed
[10:23] schestowitz in tmux you can see the reqs/second for tuxmachines (old server) decreasing. avg over xmas and all 8.8/sec, now about half that, as traffic gets into the new machine.
[10:26] Techrights-sec yes, the rates are slowing
[10:26] Techrights-sec however, it was only that the VMs were copied as-is and no OS upgrade or change?
[10:26] schestowitz yes, one container migration will follow at a time... to reduce complexity
[10:27] schestowitz remember that one of 5 DBs (TuxMachines Drupal) is still not migrated successfully to the DB container
[10:28] schestowitz the plan is, each CMS will then have its own FS/container, so that's 5 containers at least
[10:28] schestowitz FS as in filespace, not filesystem
[10:30] schestowitz The old days: -) http://www.tuxmachines.org/gallery/v/pclos092/pclos09_2_ff2.jpg.html Slashdot 10+ years ago
[10:30] -TechrightsSocial/#boycottnovell-social-www.tuxmachines.org | pclos09.2_ff2
[10:38] Techrights-sec container or vm?
[10:38] Techrights-sec \
[10:38] schestowitz I am actually not sure if the machines we now access as the new server are themselves containers rather than VM, I can check on the hypervisor
[10:39] schestowitz hypervisor on 114, you have credentials for it
[10:41] schestowitz lxc-start -n techrights-old
[10:41] schestowitz as root, assuming you're in sudoers
[10:41] schestowitz BUT
[10:41] schestowitz don't run it
[10:42] schestowitz it is already running
[10:42] schestowitz sudo lxc-attach -n viera for IRC bot
[10:42] Techrights-sec ok wont't test for a bit yet
[10:43] schestowitz so no more virtual machines basically and I suppose performance can improve as a result, too
[10:50] schestowitz testing performance on the zero-traffic machine for various notorious slow pages
[10:52] schestowitz TODO:
[10:52] schestowitz add missing irc post, test
[10:52] schestowitz update backup scripts
[10:52] schestowitz update irc and raspi scripts
[10:53] schestowitz observation: site noticeably faster now and with that many cpu cores I doubt additional traffic would strain things
[10:54] schestowitz maybe the backup-related downtimes will almost go away as well
[10:56] schestowitz TM feels lightening fast now, like less than a second to load a page
● Dec 31
[11:16] Techrights-sec Ok. I can log into hv and have access via sudo. I won't test anything beyond
[11:16] Techrights-sec that for now.
[11:16] Techrights-sec I can check the DNS here in about 45 minutes, the TTL is that long.
[11:16] Techrights-sec I guess we forgot to ramp own the TTL for the changeover.
[11:17] schestowitz is that something we can improve when switching TECHRIGHTS.ORG /COM / BN.com over?
[11:18] schestowitz (I have not directed Catalyst2 to do this yet, am still testing here and there... and I think you should add you to list of authorised persons for that, just in case I get hospitalised or worse)
[11:21] Techrights-sec Yes. I'm not sure how commonly known it is but in the hours leading up
[11:21] Techrights-sec to the switch over of DNS reduce the TTL. It increass the load of the
[11:21] Techrights-sec DNS slightly (more traffic) but then the change over lasts only as long
[11:21] Techrights-sec as the final TTL. So if the TTL is now an hour it can be set to a 5 minutes
[11:21] Techrights-sec or ramped down gradually. But then once it reaches 1 minute, switch over
[11:21] Techrights-sec then the site can only be unavailable for up to 1 minute for any given visitor
[11:21] Techrights-sec should they hit the DNS at just the wrong minute.
[11:21] schestowitz I do not know how to change those settings
[11:22] Techrights-sec It has been a Very Long Time (tm) since I did it so things will be new
[11:22] Techrights-sec all over again.
[11:22] Techrights-sec I presume it will be somewhere on the catalyst2 web interface?
[11:23] schestowitz the thing is, I asked them to do this for me, to reduce the chance of my making a mistake. They said it would apply within no more than 10 mins. Are you OK with me switching over the three techrights domain names now and maybe mention to them TTL?
[11:26] schestowitz is the net benefit just quicker passover from one address to the next and nothing else? because I don't mind taking a day off from posting today and tomorrow
[11:26] Techrights-sec The TTL needs to be done first. Then once the DNS records reflect the new TTL
[11:26] Techrights-sec it will be time to change over. Then after the change over the TTL
[11:26] Techrights-sec can be put back to the old, longish value.
[11:26] Techrights-sec Doing it in a different order has no benefit.
[11:29] Techrights-sec The benefit is fewer visitors going to the old site once the new one becomes
[11:29] Techrights-sec active.
[11:29] Techrights-sec Less disruptive for them.
[11:29] Techrights-sec The first time I helped with that we did it with a very busy site and
[11:29] Techrights-sec there was noone who noticed, among those that were watching for problems.
[11:29] Techrights-sec So it went that smoothly.
[11:29] schestowitz I will ask catalyst2
[11:35] Techrights-sec BTW TM is calling itself tuxmachines-old and it is itself using Quad9 for DNS
[11:35] Techrights-sec lookups.
[11:35] Techrights-sec That is based in California.
[11:35] schestowitz maybe it is inherited from the HV?
[11:35] schestowitz BTW, it is called "old" because the "new" would be alpine with containers, the proper way
[11:38] schestowitz Hithank you for the quick response, that has worked really wellWe now have the bigger site to switch over, it's accessed over techrights.org techrights.com and boycottnovell.com ... and I'm told that changing TTL prior to changeover the time taken to move over to the news DNS can be reduced but I don't know how/if this can be done. The new IP address for this site (all domains are the same) is 23.161.112.116
[11:44] schestowitz Ok so techrights.org techrights.com and boycottnovell.com should be switched over to 23.161.112.116 also?yes, this is a different address from the one for TuxMachinesOk Ill add that to the ticket and get it processedthank you so much!
[11:45] schestowitz No prob, will let you know when complete
[11:46] schestowitz yes, this is a different address from the one for TuxMachines
[11:50] schestowitz just blocked news-roundup category in TR due to ddos-ish, load avg 70+. We'll need to move monitoring over to the new server soon and redo the session of tmux as suits us both (we don't always use same screen size and some stuff we no longer need to do/monitor
[11:53] schestowitz I am guessing to stress-test TM now using social control media links
● Dec 31
[12:01] schestowitz new traffic starting to arrive at new TR server, TM seems to now take most traffic (maybe 80%) from the new server
[12:02] Techrights-sec Excellent
[12:03] schestowitz It's a lot easier to test AFTER the changeover, rianne had a go at TM and could not find any issues, but sometimes the wrong server is reached (still, round robin scheduled for DNS allocation I assume)
[12:03] schestowitz It's a lot easier to test AFTER the changeover, rianne had a go at TM and could not find any issues, but sometimes the wrong server is reached (still, round robin scheduler for DNS allocation I assume)
[12:04] Techrights-sec Yes, chech the TTL to see how long she must wait to get the new IP from DNS
[12:05] schestowitz 15 23.161.112.115 (23.161.112.115) 172.377 ms 172.352 ms 174.390 ms
[12:05] schestowitz from traceroute here
[12:06] Techrights-sec Traceroute does the packet ttl for TCP or UDP not the DNS record
[12:06] Techrights-sec see dig or similar
[12:06] Techrights-sec ]
[12:07] schestowitz ;; Query time: 59 msec
[12:08] schestowitz Query time: 931 msec for techrights.org
[12:12] schestowitz I have just restored access to news-roundup and will reset apachetop on tm and tr (old server) to better assess how much traffic they receive in recent mins/hours
[12:12] Techrights-sec techrights.org. 3600 IN A 23.161.112.116
[12:12] Techrights-sec ;; Query time: 287 msec
[12:12] Techrights-sec ;; SERVER: 9.9.9.9#53(9.9.9.9)
[12:12] Techrights-sec ;; WHEN: Thu Dec 31 12:06:47 2020
[12:12] Techrights-sec ;; MSG SIZE rcvd: 48
[12:12] Techrights-sec 3600
[12:12] Techrights-sec seconds
[12:12] Techrights-sec wit hthe new address
[12:15] schestowitz OK, changed and shuffled a bit in old tmux, I'll be relaxed when each site is at less than 1 req/sec on the old one. I'll configure tmux on "new"
[12:20] schestowitz I don't think we need the pane for htop now that we have nmon with graphs, correct? waste of space...
[12:28] Techrights-sec ok no htop
[12:29] schestowitz ok, go to new tr (.116) and run monitor-techrights, change as suits you as well
[12:29] schestowitz I now have two tmux sessions, one for new another for old
[12:31] schestowitz dig techrights.org
[12:31] schestowitz 199.19.78.19
[12:31] schestowitz ;; Query time: 252 msec
[12:32] schestowitz dig techrights.com
[12:32] schestowitz 23.161.112.116
[12:32] schestowitz ;; Query time: 65 msec
[12:32] schestowitz dig boycottnovell.com
[12:32] schestowitz 199.19.78.19
[12:32] schestowitz ;; Query time: 895 msec
[12:35] Techrights-sec ok my dns now directs to the new machine
[12:37] schestowitz Mine still flaps a bit as I run dig periodically, but it's getting there and for tuxmachines it's sending most traffic to new
● Dec 31
[13:02] schestowitz "The A record has been updated. Please allow up to 24hrs for propagation to occur"
[13:02] schestowitz "techrights.org techrights.com and boycottnovell.com are now on 23.161.112.116"
[13:22] schestowitz Let's take time to think of a multi-party strategy with the Intel story, maybe series title will be InteLeaks
[13:38] schestowitz installing sshpass on the pi here, will set things for pi/root to be able to upload daily stuff without human intervention
[13:38] schestowitz I want to pass time doing much needed work while not posting anything as the sites flap
● Dec 31
[14:14] schestowitz I am cronning ipfs updates at the moment and preventing anyone else from having keyless access to the server
[14:16] schestowitz with IP changes I think now is a good time to revise the crontabs on the servers as well
[14:19] schestowitz pi cron job set to update the ipfs txt and html index every hour between 1am and 5am each day
[14:29] schestowitz next, automating the irc log generation, with i/o going to file so I can check the process for sanity when I wake up
[14:38] schestowitz OK, /home/links will be updated each day 3am U/GMT
[14:42] schestowitz cp output.txt /home/links/ipfs/ will be run as well, that's the output of the run, in case there are errors to be found or something bad in the output file for WordPress, so there's a copy
[14:42] Techrights-sec ack
[14:42] Techrights-sec Wouldn't an hour or two earlier be better?
[14:43] schestowitz it would, but... longstanding issue is, WordPress server clock/CMS clocks not the same. the server is US east coast time, so IPFS stuff runs until 5am our time (UK) for a given day
[14:44] schestowitz usually if I write additional things between bulletin and 5am I can just regenerate the bulletin afterwards
[14:46] schestowitz tail -5 /home/links/ipfs/output.txt && uptime
[14:46] schestowitz Bandwidth
[14:46] schestowitz TotalIn: 5.9 GB
[14:46] schestowitz TotalOut: 2.3 GB
[14:46] schestowitz RateIn: 16 kB/s
[14:46] schestowitz RateOut: 5.1 kB/s
[14:46] schestowitz 14:46:23 up 2 days, 22:12, 3 users, load average: 0.90, 0.99, 1.02
[14:47] schestowitz tail -18 /home/links/ipfs/output.txt | head -n 1
[14:47] schestowitz This page was last modified on Thu 31 Dec 14:36:55 GMT 2020
[14:48] schestowitz "pi" user will reupload this pair of files until 5am, then the next day again
● Dec 31
[15:02] schestowitz 40 02 * * * /home/roy/yesterday-irc.log.sh > /home/roy/output.txt
[15:02] schestowitz 05 03 * * * kate /home/roy/output.txt
[15:04] schestowitz the second one, I think, will forcibly remind me to check the sanity of it and then maybe see the ipfs index to ensure all went well at the pi as well, without having to actually access it
[15:21] Techrights-sec The second one will need to set the environment variable.
[15:21] Techrights-sec for the display, for the logged in user:
[15:21] Techrights-sec 05 03 * * * DISPLAY=:0.0 /home/roy/output.txt
[15:21] Techrights-sec Set it to a few minutes from now and test.
[15:21] Techrights-sec 05 03 * * * DISPLAY=:0.0 kate /home/roy/output.txt
[15:21] Techrights-sec I forgot the editor in the first one
[15:21] schestowitz will fix
[15:22] schestowitz it looks like you already readded the irc blog post to the new server? It's confusing me that it's always showing up
[15:22] schestowitz 23.161.112.115 tuxmachines.org
[15:22] schestowitz 23.161.112.115 www.tuxmachines.org
[15:22] schestowitz 23.161.112.116 techrights.org
[15:36] schestowitz 05 03 * * * DISPLAY=:0.0 falkon http://techrights.org/ipfs
[15:36] -TechrightsSocial/#boycottnovell-social-techrights.org | Techrights Full IPFS Index
[15:38] Techrights-sec I haven't changed any cron tabs yet.
[15:38] Techrights-sec I'll wait till th edust settles a little before poking artound.
[15:39] schestowitz makes sense; I did after some hours realise that I was looking at the new site in fact and that IRC blog post had already been reposted in it, which is good (I just didn't expect that)
[15:45] schestowitz I have just checked old TM, over the past few hours it served as much as the new, 23k hits each. I'm checking to ensure nobody submits story/comment to old as that would be lost when we wipe clean the old server
[15:50] schestowitz remember we can keep the existing centos container for utilities that are not quite web-facing
[15:59] Techrights-sec The existing old one could be updated then.
[15:59] schestowitz yes, after critical services like httpd and all are moved entirely out of that ageing container
● Dec 31
[16:00] schestowitz I updates the "hosts" file on rianne's laptop and mine so now we resume posting in tuxmachines (assuming people's DNS servers are mostly updated) and will resume techrights later, at least Daily Links
[16:00] schestowitz *updated
[16:19] Techrights-sec Probably not. BTW is Scotland in a position to reject Brexit?
[16:20] schestowitz It already rejects it, even publicly, based on a statement I saw mentioned in counterpunch (Binoy) 2 days ago. IndyRef might follow.
[16:21] schestowitz Heck, if they do this, and as they speak English, they could braindrain Wales and England
[16:22] schestowitz http://schestowitz.com/royrianne/gallery/index.php/Edinburgh
[16:22] -TechrightsSocial/#boycottnovell-social-schestowitz.com | Edinburgh
[16:22] Techrights-sec It would pull in a lot of escapees if they are able to rejoin the EU quickly or
[16:22] Techrights-sec even flat out reject Brexit.
[16:25] Techrights-sec I guess visits to various Royal gardens are out for the foreseeable future.
[16:25] Techrights-sec Same for garden shows.
[16:39] schestowitz I am doing some checks, found out we use https://downloads.mariadb.org/mariadb/5.5.56/
[16:39] -TechrightsSocial/#boycottnovell-social-downloads.mariadb.org | MariaDB 5.5.56 Stable - MariaDB
[16:44] Techrights-sec 5.x is really far behind. It might not be a fully automated upgrade to get
[16:44] Techrights-sec to 10.x or 11.x
[16:45] schestowitz should brian kerbs be in automated links?
[16:45] schestowitz I want to support folks who do their own thing, esp. if they know what they cover
[16:46] Techrights-sec Krebs? Ok. I can see if there is a feed to add.
[16:46] Techrights-sec https://krebsonsecurity.com/feed/
[16:47] schestowitz in 2021 I think we ought to speed up our retreat from the "burning platforms" of PR as "media"
[16:48] schestowitz I am trying not to link to either TM or TR today, knowing many will get 404s because of outdated DNS upsteam. People can forgive for not posting on last/first day of a year...
[16:49] schestowitz https://www.bbc.co.uk/news/election-us-2020-55494005
[16:49] -TechrightsSocial/#boycottnovell-social-www.bbc.co.uk | Republican senator to dispute certification of Biden victory - BBC News
[16:51] Techrights-sec git needs tweaking, but otherwise the updated files are in place on TR
[16:51] Techrights-sec Krebs' feed will be checked starting tomorrow. He goes for quality not
[16:51] Techrights-sec quantity so there may be some delay before any posts of his show up,
[16:51] Techrights-sec aside from the site anniversary announcement.
[16:51] Techrights-sec Yeah, there will be little of substance for the next 96 hours or so.
[16:51] Techrights-sec I will check a few sites anyway.
[16:52] schestowitz with the sites on the other side of the DC space, at least my biggest xmas worry is mostly behind now, I can relax a bit. No signs of anything broken or missing data yet.
● Dec 31
[17:01] schestowitz new tmux session has wasted space as nmon does not scale fully horizontally. Anything else we need on screen?
[17:02] schestowitz how's this? shows cpu strain only when above 70%
[17:03] Techrights-sec Not that I can think of. You are more familiar with site monitoring at
[17:03] Techrights-sec that level.
[17:03] Techrights-sec FWIW I have maximized the window on my side, so any space there can be used,
[17:03] Techrights-sec but not any additional expansion.
[17:03] Techrights-sec Ok. Low system loads are probably not so important.
[17:03] Techrights-sec Too bad there is not a more recent version of tmux there,
[17:03] Techrights-sec otherwise we could label the panes.
[17:03] schestowitz the monitoring can be put on any machine, inc. this pi of even this ytalk session
● Dec 31
[18:33] *TechrightsSocial has quit (Remote host closed the connection)
[18:34] *TechrightsSocial (~b0t@23.161.112.116) has joined #boycottnovell-social
[18:34] TechrightsSocial Hello World! I'm TechrightsSocial running phIRCe v0.77
● Dec 31
[19:01] *liberty_box has quit (Ping timeout: 256 seconds)
[19:01] *rianne_ has quit (Ping timeout: 256 seconds)
[19:46] *rianne_ (~rianne@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social
[19:47] *liberty_box (~liberty@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social
[19:52] *rianne_ has quit (Ping timeout: 240 seconds)
[19:53] *liberty_box has quit (Ping timeout: 246 seconds)
[19:55] *rianne_ (~rianne@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social
[19:55] *liberty_box (~liberty@81.154.173.106) has joined #boycottnovell-social
● Dec 31
[20:12] *liberty_box has quit (Ping timeout: 260 seconds)
[20:12] *rianne_ has quit (Ping timeout: 256 seconds)
[20:27] *liberty_box (~liberty@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social
[20:27] *rianne_ (~rianne@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social
● Dec 31
[23:28] *rianne_ has quit (Ping timeout: 240 seconds)
[23:28] *liberty_box has quit (Ping timeout: 240 seconds)