●● IRC: #boycottnovell @ FreeNode: Saturday, February 27, 2021 ●● ● Feb 27 [00:26] *randomgry (~test@unaffiliated/gryllida) has joined #boycottnovell [00:26] *gry has quit (Ping timeout: 272 seconds) [00:30] *randomgry is now known as gry ● Feb 27 [01:40] *liberty_box has quit (Ping timeout: 256 seconds) [01:56] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell ● Feb 27 [03:57] *liberty_box has quit (Ping timeout: 272 seconds) ● Feb 27 [04:00] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell ● Feb 27 [05:06] *liberty_box has quit (Ping timeout: 276 seconds) [05:48] *gry has quit (Ping timeout: 276 seconds) ● Feb 27 [06:14] *gry (~test@unaffiliated/gryllida) has joined #boycottnovell [06:36] *gry has quit (Ping timeout: 265 seconds) [06:41] *gry (~test@unaffiliated/gryllida) has joined #boycottnovell [06:56] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell ● Feb 27 [07:31] *rianne_ (~rianne@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [07:35] schestowitz__ > Hi :-) and thank so much for the lovely article I've just seen! Very [07:35] schestowitz__ > kind, and great about cyling them round; glad you like them, and many [07:35] schestowitz__ > thanks again. [07:45] schestowitz__ > Greetings, [07:45] schestowitz__ > Sorry for the delayed response. I took a look at the capsule and it [07:45] schestowitz__ > looks like you have a lot of great content. It is unfortunately not well [07:45] schestowitz__ > structured for how spacewalk works (but is undoubtedly a good and [07:45] schestowitz__ > functional structure in general). [07:45] schestowitz__ > [07:45] schestowitz__ > Spacewalk works based on page hash comparrison. Since your capsule moves [07:45] schestowitz__ > things into pages based on month/year, spacewalk would only see an [07:45] schestowitz__ > update every month or year... rather than every time you add a new [07:45] schestowitz__ > article. I am unfortunately, and with regrets, not able to update a link [07:45] schestowitz__ > to the current month folder every time the month changes. [07:45] schestowitz__ > [07:46] schestowitz__ > I definitely support what y'all are doing and if you end up with a page [07:46] schestowitz__ > that shows maybe the top 10 or 20 most recent posts sorted by date or [07:46] schestowitz__ > hte like I'd be happy to include it as a part of the spacewalk feed. I [07:46] schestowitz__ > know making something extra just for this feed is probably out of scope [07:46] schestowitz__ > for you, but wanted to offer just in case you were interested. [07:46] schestowitz__ > [07:46] schestowitz__ > Be in touch and let me know how you'd like to proceed. If more [07:46] schestowitz__ > information on how spacewalk works would be helpful I can provide that [07:46] schestowitz__ > as well. [07:46] schestowitz__ > [07:46] schestowitz__ > Best wishes, [07:46] schestowitz__ Hi, [07:46] schestowitz__ How about [07:46] schestowitz__ gemini://gemini.techrights.org/daily-feed [07:46] schestowitz__ and also [07:46] schestowitz__ gemini://gemini.techrights.org/feed [07:46] schestowitz__ Let me know if that works better or needs further work. [07:46] schestowitz__ Regards, ● Feb 27 [08:04] *liberty_box has quit (Ping timeout: 264 seconds) [08:04] *rianne__ (~rianne@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [08:04] *rianne_ has quit (Read error: Connection reset by peer) [08:04] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [08:50] schestowitz__ > Former media advisor Brittany Higgins[1] went public about 2 weeks ago, [08:50] schestowitz__ > claiming [08:50] schestowitz__ > [08:50] schestowitz__ > a) rape on the sofa of female defense minister, [08:50] schestowitz__ > [08:50] schestowitz__ > b) she didn't specify the suspect's name (Lehrmann), reports suggest her [08:50] schestowitz__ > gripe is with the Government for helping suspect make a clean getaway, [08:50] schestowitz__ > officials even steam cleaned the sofa before the police could check it [08:50] schestowitz__ > [08:50] schestowitz__ > Even though she never told anybody the name of the suspect, three other [08:50] schestowitz__ > women immediately made complaints about the same suspect [08:50] schestowitz__ > [08:50] schestowitz__ > I can't help wondering, if this guy had the same profile as Appelbaum, [08:50] schestowitz__ > would there be even more women with the same concerns as the first four? [08:50] schestowitz__ > [08:50] schestowitz__ > The cover up is a story in itself, it involves the most senior officials [08:50] schestowitz__ > in a G20 government, that potentially makes it a lot bigger than the [08:51] schestowitz__ > Alex Salmond stuff. Australia also seems to have much more intense [08:51] schestowitz__ > injunctions such as the Securency super-injunction and the injunction [08:51] schestowitz__ > that concealed the case against Cardinal George Pell. [08:51] schestowitz__ > [08:51] schestowitz__ > https://www.theguardian.com/commentisfree/2014/jul/30/wikileaks-gag-order-open-justice-is-threatened-by-super-injuctions [08:51] -TechrightsBN/#boycottnovell-www.theguardian.com | WikiLeaks gag order: open justice is threatened by super-injunctions | Australia news | The Guardian [08:51] schestowitz__ > [08:51] schestowitz__ > It seems that both techrighs and kangaroocourtofaustralia.com have been [08:51] schestowitz__ > shadow banned by Twitter and Facebook, so you have something in common [08:51] schestowitz__ > [08:51] schestowitz__ > The media are having a field day with it because there are so many [08:51] schestowitz__ > pictures of the victim alongside powerful figures: [08:51] schestowitz__ > [08:51] schestowitz__ > https://www.qt.com.au/news/what-speaker-knew-about-rape-claims/4199321/ [08:51] schestowitz__ > [08:51] -TechrightsBN/#boycottnovell-www.qt.com.au | ACCESS TO SUITE: List of staffers who knew of incident | Queensland Times [08:51] schestowitz__ > and also because everybody is obviously lying, even a junior journalist [08:51] schestowitz__ > might get lucky exposing a lie with the right question [08:51] schestowitz__ > [08:51] schestowitz__ > I might write something comparing the way Lehrmann's name has been [08:51] schestowitz__ > protected against the way Appelbaum and Assange where deliberately shamed. [08:51] schestowitz__ I generally know so little about these Aussie affairs that I'd rather not touch it myself, for fear I might write something wrong. [08:51] schestowitz__ Twitter went further than shadow-banning. [08:51] schestowitz__ Compare [08:51] schestowitz__ http://techrights.org/2021/01/28/twitter-censorship-regime/ (January) [08:51] schestowitz__ to [08:51] -TechrightsBN/#boycottnovell-techrights.org | Twitter is Hiding Techrights and Partly Shadowbans Yours Truly | Techrights [08:51] schestowitz__ http://techrights.org/2021/02/04/twitter-berserk/ (Feb) [08:51] schestowitz__ and one day later: [08:51] -TechrightsBN/#boycottnovell-techrights.org | Twitter: We Suspend Your Account For Quoting the Media About Bill Gates | Techrights [08:51] schestowitz__ http://techrights.org/2021/02/05/twitter-censorship-bingo/ [08:51] schestowitz__ Afterthought (an hour ago): [08:51] -TechrightsBN/#boycottnovell-techrights.org | Twitter Has Just Suspended the President of FFII for Naming Bill Gates Patent Profiteering and Factual Information About Twitter Censorship (Updated) | Techrights [08:51] schestowitz__ Another example for the mix is RMS. [08:51] schestowitz__ The whole thing "started" with a mailing list post, which was almost understandably controversial. [08:51] schestowitz__ But he was cancelled for many women online then saying things about him, about things he's alleged to have "thought" ages ago. Or even outright fabrications (never corrected), e.g.: [08:51] schestowitz__ http://techrights.org/2020/09/10/the-fake-door-sign/ [08:51] schestowitz__ The damage is done: [08:51] -TechrightsBN/#boycottnovell-techrights.org | The Fake Door Sign Used to Frame Richard Stallman and Misrepresent Him One Year Ago (the Media Never Corrected This Slanderous Allegation) | Techrights [08:51] schestowitz__ http://techrights.org/2020/09/10/sjvn-senior-moment/ [08:51] schestowitz__ https://joindiaspora.com/posts/20164558#e8ff1410598e0139c9a122bfe022ffdd [08:51] -TechrightsBN/#boycottnovell-techrights.org | One Year Later Steven J. Vaughan-Nichols Libel Against Richard Stallman Remains Online and Uncorrected at ZDNet | Techrights [08:51] -TechrightsBN/#boycottnovell-@linux@joindiaspora.com: Can Linux Run Video Games? http://www.tuxmachines.org/node/148125 [08:51] schestowitz__ "dude, it depends on the hardware, come on... are you trolling?" [08:51] -TechrightsBN/#boycottnovell--> www.tuxmachines.org | Can Linux Run Video Games? | Tux Machines [08:52] schestowitz__ "it cant sorry, you need to switch to windows" [08:52] *rianne__ has quit (Ping timeout: 264 seconds) [08:53] *liberty_box has quit (Ping timeout: 276 seconds) [08:54] *rianne__ (~rianne@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [08:55] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell ● Feb 27 [09:35] schestowitz__
  • [09:35] schestowitz__
    Mageia 8 Linux distro ready for download
    [09:35] schestowitz__
    [09:35] -TechrightsBN/#boycottnovell-betanews.com | Mageia 6 Linux distribution now available for download [09:35] schestowitz__

    "ARM support has continued to develop, with both AArch64 and ARMv7 now having all packages built and being close to primary architectures now. Support for Wi-Fi installation in the classical installer using WPA2 encryption has been added, as well as improved support for newer filesystems allowing installations on F2FS. Support for NILFS, XFS, exFAT and Windows 10 NTFS has been improved to allow for better [09:35] schestowitz__ partition management," says Donald Stewart, Mageia developer.

  • [09:37] schestowitz__
  • [09:37] schestowitz__
    Getting Started with LibreOffice 7.0 Guide Just Arrived!
    [09:37] schestowitz__
    [09:37] schestowitz__

    The Documentation Team is happy to announce the immediate availability of the LibreOffice 7.0 Getting Started Guide, updated to include all LibreOffice 7.0 features.

    [09:37] -TechrightsBN/#boycottnovell-blog.documentfoundation.org | Getting Close to LibreOffice 4.1 - The Document Foundation Blog [09:37] schestowitz__

    The guide is written for anyone who wants to get up to speed quickly with LibreOffice. Readers may be new to office software, or may be familiar with another office suite. This guide is a valuable asset for all users.

  • ● Feb 27 [10:14] *liberty_box has quit (Ping timeout: 240 seconds) [10:15] *rianne__ has quit (Ping timeout: 276 seconds) [10:15] schestowitz__ I have put DB login details in my personal notes. I was going to send a more complete formula over ssh, but I see you got it anyway [10:39] schestowitz__ BTW, I still toggle logging on and off for Gemini, so the file is never complete. Over the past 2 days, however, due to growing strain from spiders, I left it on for longer periods of time. It helps to know how much it affects our connection and what the limits/bottlenecks are. Gemini is small, so I think a million requests per day can be barely noticeable. To us in the house anyway... [10:39] schestowitz__ IOW, for something compact like gem text I don't foresee a need to host from outside one's premises [10:40] schestowitz__ In the days of gophers you'd assume modem connections, so no 10MB per page midset [10:40] schestowitz__ In the days of gophers you'd assume modem connections, so no 10MB per page mindset [10:40] Techrights-sec Yeah. Though I am wondering specifically which parts the one bot was [10:40] Techrights-sec looping through the other day. [10:41] schestowitz__ I keep an eye on the gemini mailing lists now but have not subscribed as there it too much and lots of OT stuff [10:42] Techrights-sec gopher and wearly web were concurrent. [10:42] Techrights-sec LOTS of off topic stuff there, too bad. [10:44] Techrights-sec There are also a lot of people [10:44] Techrights-sec that don'tr / won't understand what document metadata is. Where it is useful [10:44] Techrights-sec and whether there should be some in Gemini text is another matter, but [10:44] Techrights-sec it's hard to discuss when many don't grasp the topic. Which is a major puzzle [10:44] Techrights-sec since many claim to be in ICT yet lack core knowledge and some major concepts. [10:44] Techrights-sec The TR browsing structure is only possible because there was a way to [10:44] Techrights-sec smuggle date and title of documents through the workflow to the end stage. [10:45] Techrights-sec At the end of the day it is about ke-value pairs. Fighting over the semantic [10:45] Techrights-sec contents is pointless. Perhaps that this their goal, to bog it down [10:45] Techrights-sec with concern trolling and fake misunderstanding. [10:51] Techrights-sec I'm not sure adding metadat to gemini files is good, I am not sure it is bad. [10:51] Techrights-sec But it is frustrating that while some clearly understand, and that is good, [10:51] Techrights-sec many appear to refuse to understand the concepts. [10:51] Techrights-sec Anyway, with direct access to the MariDB database through SQL, it will b [10:51] Techrights-sec e possible to streamline and simplify the generation of pages. [10:51] Techrights-sec It's more of an exercise in principle now, but doing it that way [10:51] Techrights-sec is more likely to be reusable by other projects. [10:51] schestowitz__ ime, what's lacking is documenting (project's generic name isn't helping), so we need to document, cover, advocate, just spread gemini:// links etc. [10:52] schestowitz__ For a large site focused on tech news we can become an early show case >on a large scale< and I think this gives us some influence over the direction taken as nothing is yet set in stone or standardised [10:53] Techrights-sec ts would come from pacakging [10:53] Techrights-sec some clients for various distros. [10:53] schestowitz__ I can poke some DDs, but not sure of the procedures followed [10:54] Techrights-sec Agreed, but one of the biggest advancements would come from pacakging [10:54] Techrights-sec some clients for various distros. [10:56] Techrights-sec It's more of a few skill levels below DD [10:56] Techrights-sec even I could probably package, if I had a dedicated system and ensured that [10:56] Techrights-sec I could commit to setting time aside for a cycle or two. [10:57] schestowitz__ it might be best for the original s/w devs to do/propose, then pass to a DD/DM with keyring access [10:57] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [10:57] *rianne__ (~rianne@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [10:57] schestowitz__ iow, I think it's well outside our scope and priority. Some of the main tools rely on the BLOAT of rust cargo cult, which having explored on arm the other day, I now regard to be as bad as Electron [10:58] schestowitz__ frameworks and bloat are now seen as benign and simple tools as malicious and dangerous ● Feb 27 [11:02] schestowitz__ I always feel a bit guilty about logging gemini, knowing what this project is inherently against, but I'm sure others too pursue some sort of diagnostics, which makes sense when one address can make half a million reqs in several hours. Should we package something up to that effect? Maybe as means of DDOS protection? Surely it'll become a real issue in coming months/years. [11:03] schestowitz__ I added gawk as a dependency for dates in the logs [11:04] schestowitz__ iftop -i wlan0 -P -t -L 1000 | grep -B 0 -A 1 :1965 | grep -v :1965 | gawk '{ print strftime("[%Y-%m-%d %H:%M:]"), $0 }' >> /home/gemini/log.txt ● Feb 27 [12:30] Techrights-sec sudo tcpdump --direction=in -l -tttt -i wlan0 'tcp[tcpflags] & (tcp-syn) != 0 and port 1965' | awk '{sub(/\.[0-9]+$/,"",$2); sub [12:30] Techrights-sec (/\.[0-9]+$/,"",$4); print $1, $2, $4;}' [12:30] Techrights-sec more accurate than iftop [12:30] schestowitz__ let's try that... [12:33] schestowitz__ it seems to work ok so far, and with more real-time-like traits [12:34] Techrights-sec tcpdump may have to be added, but it is the mainstay of network toolboxes every- [12:34] Techrights-sec where [12:34] Techrights-sec also throw in a -p there in the tcpdump part [12:36] schestowitz__ cat log_gemini_new.sh [12:36] schestowitz__ tcpdump -p --direction=in -l -tttt -i wlan0 'tcp[tcpflags] & (tcp-syn) != 0 and port 1965' | awk '{sub(/\.[0-9]+$/,,); sub(/\.[0-9]+$/,,); print , , ;}' >> /home/gemini/log.txt [12:38] schestowitz__ corrected now, lost some bits [12:40] schestowitz__ show-new-visitors.sh may now need amending. I kept the old version of the logger aside (old filename). [12:41] Techrights-sec yes and it won't miss connections [12:41] Techrights-sec it is precise since the gemini protocol has one-one for connections and request [12:41] Techrights-sec ^ tario [12:41] Techrights-sec ratio [12:41] Techrights-sec ok I'll check the script [12:46] *rianne__ has quit (Ping timeout: 240 seconds) [12:46] *liberty_box has quit (Ping timeout: 240 seconds) [12:49] Techrights-sec the show-new-visitors.sh can be simplified to just contain tail [12:49] Techrights-sec all set [12:49] Techrights-sec remember the >> append redirect? [12:54] *rianne__ (~rianne@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [12:56] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell ● Feb 27 [13:17] schestowitz__ did the port change or something? I've been struggling here, can't figure out why it's not writing anything with either network tool [13:19] Techrights-sec sudo tcpdump --direction=in -p -l -tttt -i wlan0 'tcp[tcpflags] & (tcp-syn) != 0 and port 1965' | awk '{sub(/\.[0-9]+$/,"",$2); [13:19] Techrights-sec sub(/\.[0-9]+$/,"",$4); print $1, $2, $4;}' >> /home/gemini/log.txt [13:19] Techrights-sec it has to write to expected location [13:19] schestowitz__ either the new or the old one-liner would not write to that file anymore and it does not seem to be a permissions issue (I checked loads of things) [13:23] Techrights-sec ok. on the RPi it must be:\ [13:23] Techrights-sec sudo tcpdump --direction=in -p -l -tttt -i wlan0 'tcp[tcpflags] & (tcp-syn) != 0 and port 1965' | awk '{sub(/\.[0-9]+$/,"",$2); [13:23] Techrights-sec sub(/\.[0-9]+$/,"",$4); print $1, $2, $4;fflush();}' >> /home/gemini/log2.txt [13:23] Techrights-sec adjust the log name as needed [13:33] schestowitz__ now=`date +"-%Y-%m-%d"` [13:33] schestowitz__ echo '----------------------------------------------------------------------------' >> /home/gemini/gemini-log${now}.txt [13:33] schestowitz__ echo -n 'Restarting logging at ' >> /home/gemini/gemini-log${now}.txt [13:33] schestowitz__ date >> /home/gemini/gemini-log${now}.txt [13:33] schestowitz__ echo '' >> /home/gemini/gemini-log${now}.txt [13:33] schestowitz__ # tcpdump -p --direction=in -l -tttt -i wlan0 'tcp[tcpflags] & (tcp-syn) != 0 and port 1965' | awk '{sub(/\.[0-9]+$/,"",$2); sub(/\.[0-9]+$/,"",$4); print $1, $2, $4;}' >> /home/gemini/log.txt [13:33] schestowitz__ sudo tcpdump --direction=in -p -l -tttt -i wlan0 'tcp[tcpflags] & (tcp-syn) != 0 and port 1965' | awk '{sub(/\.[0-9]+$/,"",$2);sub(/\.[0-9]+$/,"",$4); print $1, $2, $4;fflush();}' >> /home/gemini/gemini-log${now}.txt [13:34] schestowitz__ The viewer may need to be adapted somewhat for this, I think having a separate directory like ~/log is worthwhile too [13:36] Techrights-sec a separate directory is probably a good idea [13:37] schestowitz__ you have just made one [13:39] schestowitz__ ok, it's now running and writing correctly to the right file/s [13:46] schestowitz__ just tidied up ~ a little with subdirs [13:47] Techrights-sec yes, see also ~?bin/tcpdump-logger.sh [13:47] Techrights-sec much improved [13:47] schestowitz__ checking.. [13:53] schestowitz__ imported to "pi" the more elegant script (bash) and reran with files set afresh (binned the older files in /tmp ) [13:56] schestowitz__ do you want to modify show-new-visitors.sh or should I? File location changed (dynamic) and maybe the format too needs adapting to (awk) [13:57] Techrights-sec I'll get it [13:58] schestowitz__ excellent, thanks. I was reluctant to run my old hack with cli mode top because it was too cpu-intensive to be worth it, except when diagnosing. The current implementation is a lot better and doesn't have high i/o in the mix ● Feb 27 [14:04] Techrights-sec ok I have ~/bin/tcpdump-logger.sh and ~~/bin/show-new-visitors.sh matching [14:04] schestowitz__ I have just diff'ed ~/bin/tcpdump-logger.sh and what's running. It seems not to have changed since I fused that in. [14:05] schestowitz__ except indentation? I see file change 5 mins ago. [14:07] schestowitz__ to avoid conflicts I've just put RO log_gemini_new.sh in ~gemini/bin [14:08] Techrights-sec yes tweaking, a bad habit of always changing [14:08] schestowitz__ I know my lazy quick and dirty hacks can be factorised there [14:09] schestowitz__ to make it less like spying and more like DDOS prevention is might be worth extending to give something like count of reqs per host, periodically, to highlight bw hogs [14:10] Techrights-sec then it will have to escalate in complexity [14:10] schestowitz__ that can be a separate script e.g. flag_hoarder.sh [14:12] Techrights-sec that can be in awk or perl then [14:13] schestowitz__ host in space-separated line feed is always 3rd element [14:14] schestowitz__ I typically process that with 'cut' and you could reuse some online hacks for counting and sorting by number the hostnames [14:14] schestowitz__ for multi-day 'cat' can help (aggregating files) [14:15] schestowitz__ something like cat log* | cut SOMETHING | sort THEN CRUNCH/Count [14:16] Techrights-sec $ awk '$3 {a[$3]++} END{ for (b in a) {print a[b],b}}' OFS="\t" /home/gemini/logs/gemini-log-$(date +"%F").log [14:16] Techrights-sec | sort -k1,1nr -k2,2 [14:16] Techrights-sec awk ... /home/gemini/logs/*.log [14:17] schestowitz__ this works! gee, that was fast! [14:18] schestowitz__ can be periodically run with 'clear' and maybe two-pane tmux for ~/bin/show-new-visitors.sh [14:18] schestowitz__ would decrease the number of command we need to run rather than monitoring pane to observe [14:19] Techrights-sec it's awk, so low overhead [14:19] Techrights-sec watch will do that. [14:19] Techrights-sec watch awk ... [14:19] schestowitz__ maybe wrap it in a shell script on ~/bin? [14:20] Techrights-sec see the -n or --interval option [14:21] schestowitz__ I see you edit the file (.swap) [14:22] Techrights-sec lock release, sorry I forgot it was open [14:22] schestowitz__ now it is run with watch [14:22] Techrights-sec show-new-visitors-count.sh is the wrapper for the above awk [14:23] Techrights-sec It's not so efficient in that it will re-read the whole file, so the interval [14:23] Techrights-sec ought to be nice and long [14:25] schestowitz__ watch-for-heavy-users.sh is in place [14:25] schestowitz__ chmod set [14:26] Techrights-sec ok, 755 might be better permissions or 555 or 550 [14:29] schestowitz__ I think one script with fail -f was modified a bit to accomplish something different and then exit [14:32] schestowitz__ I've modified 3 lines, commented out two and brought another up to date with the filename format [14:34] schestowitz__ ./show-new-visitors-count.sh is locked, I was going to make a rule for edge case of date being added for logger shutdown/startup (something to exclude "at") [14:35] Techrights-sec see also /lib/systemd/system/gemini-tcpdump-logger.service [14:35] Techrights-sec /usr/local/sbin/tcpdump-logger.sh [14:36] Techrights-sec Oh, it is just read only [14:36] Techrights-sec now it is writable again [14:37] schestowitz__ With the daemon running the "at" thing will no longer be an issue [14:37] schestowitz__ we'll just need a policy for flushing out rotated logs or whatnot to respect privacy [14:38] *rianne__ has quit (Ping timeout: 240 seconds) [14:38] Techrights-sec logrotate can do that [14:38] schestowitz__ should I just turn off the logging from pi account? Assuming the daemon can do the same already? [14:38] *liberty_box has quit (Ping timeout: 264 seconds) [14:40] Techrights-sec yes the 'pi' account does not need to do logging now, the (ugh) systemd [14:40] Techrights-sec service does that now [14:41] schestowitz__ coming soon: Task Manager :-) OK, disabling that at the pi account now [14:43] schestowitz__ Active: active (running) since Sat 2021-02-27 14:32:24 GMT; 10min ago [14:44] schestowitz__ there are two files on logs, maybe one is from an old script that was not updated [14:45] schestowitz__ Oh, there is a missing "-log" [14:46] schestowitz__ I will override the service, comment out the current [14:53] schestowitz__ I've changed the file in /usr and restarted/reloaded the service, though it still writes logs to the old location [14:53] Techrights-sec $ sudo crontab -l | grep -Ev '^$|^#' [14:53] Techrights-sec 0 0 * * * /bin/systemctl restart gemini-tcpdump-logger.service [14:55] *rianne__ (~rianne@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [14:55] *liberty_box (~liberty@host81-154-169-167.range81-154.btcentralplus.com) has joined #boycottnovell [14:57] Techrights-sec /home/gemini/logs/gemini-2021-02-27.log is getting the input for now [14:57] schestowitz__ yes, it has gotten split into two files [14:57] schestowitz__ and I worry that the other peripheral scripts probably anticipate the form with "-log" in it ● Feb 27 [15:00] schestowitz__ show-new-visitors-count.sh for example anticipates the newer form (filename) [15:05] Techrights-sec show-new-visitors-count.sh and show-new-visitors.sh in ~/bin now [15:05] Techrights-sec look for the new file name [15:06] schestowitz__ I made some changes to location, but I cannot get my head around the fact it's still writing to the older location, no matter if I restart the service [15:06] Techrights-sec those were the only two ther looking for the old one [15:08] Techrights-sec which old location? [15:08] schestowitz__ I think that the "newer" one has "log-" or "-log" in the filename [15:15] schestowitz__ Oh, I think my commenting style in the middle broke it [15:15] schestowitz__ I also see you've just edited that out [15:19] schestowitz__ the file structure we want is /home/gemini/logs/gemini-log-$(date +"%F").log [15:20] schestowitz__ I think it boils down to inconsistent in what we thought would be the target file [15:20] schestowitz__ I think it boils down to inconsistent thinking or confusion/lack of understanding in what we thought would be the target file [15:20] Techrights-sec fixed, I think [15:20] Techrights-sec there was some weird stuff in the service script [15:21] schestowitz__ It was my fault for putting a comment in a multi-line bit [15:21] Techrights-sec There were also some invalid filters in tcpdump [15:21] Techrights-sec I'll set all the scripts to /home/gemini/logs/gemini-log-$(date +"%F").log [15:22] schestowitz__ Yes, we keep changing our stuff back and forth due to unintended lack of understanding [15:22] schestowitz__ imagine what it's like when two devs get confused over what "master" turns to, "main" or "leader" [15:24] Techrights-sec yes [15:24] Techrights-sec ok the system script is fixed, I'll copy a backup to ~/bin [15:25] schestowitz__ Cheers, I'll test what existing scripts we have. I see that logging still goes into gemini-2021-02-27.log in ADDITION to the other file? Maybe two service running at the same time? Have not checked..... [15:28] Techrights-sec Hmm. That means a bug in the systemd file, I'll get it [15:29] schestowitz__ the rest all seems to work now, I'll make it easier for me to monitor now, esp. as we tend to attract some crazy bots (two of them yesterday) [15:34] Techrights-sec KillMode=process [15:34] Techrights-sec needed to be [15:34] Techrights-sec KillMode=control-group [15:34] Techrights-sec or [15:34] Techrights-sec KillMode=mixed [15:34] schestowitz__ The IBM way of doing think. IBM is not mast... I mean, leader in Linux [15:34] schestowitz__ The IBM way of doing things. IBM is not mast... I mean, leader in Linux [15:35] Techrights-sec systemd is not about making things easier or more efficent, one look [15:35] Techrights-sec at the code belies that. What systemd appears to be about is IBM [15:35] Techrights-sec carrying through on M$ old goals of decommodifying Linux [15:35] Techrights-sec It's getting too complex for any amateur or part-timer [15:36] schestowitz__ I had to learn because all the server distros now have it ● Feb 27 [17:49] Techrights-sec IBM probably read the Halloween Documents years ago, and figured theu [17:49] Techrights-sec could beat M$ at its own game and attack Linux by wrapping it in [17:49] Techrights-sec PID1 and being the bottleneck between the kernel and GNU space [17:49] schestowitz__ might we also joke that 'Microsoft came from IBM' (in some weird sense)? [17:54] Techrights-sec Maybhe but more that IBM saw what M$ was trying to do and decided to beat them [17:54] Techrights-sec at it: docommoditization [17:54] schestowitz__ Maybe I can think of an article to do about it, but that would require os/2 research and I know too little [17:57] Techrights-sec It'd be hard to dig up the material but there was a lot at the time. M$ [17:57] Techrights-sec backstabbed IBM badly over NT vs OS/2. They led IBM into thinking that [17:57] Techrights-sec there would be applications for OS/2, at the same time M$ was acquiring [17:57] Techrights-sec partial copyright over OS/2. So later on down the road, IBM could do nothing with OS/2 because M$ shared copyright. [17:57] schestowitz__ When lawyers (of law school drop-outs) dominate companies and not techs... we all lose [17:58] Techrights-sec and MBAs. I am sure there is an inversre relationship between the [17:58] Techrights-sec number of MBAs in a company to its viability. The only problem is that [17:58] Techrights-sec the research would be in the area of "business" and so the MBAs would [17:58] Techrights-sec be the ones to decide about the research grant. [17:58] Techrights-sec THey'd block it. [17:58] Techrights-sec \ ● Feb 27 [21:48] schestowitz__ ./watch-for-heavy-users.sh now has further improvements, which will be noticed immediately if you run it. That helps me run things in one terminal instead of two.