This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
haas:status [2015/11/13 21:46] – wedge | haas:status [2022/08/28 19:25] – [Other Days] wedge | ||
---|---|---|---|
Line 5: | Line 5: | ||
* update grade not-z scripts to handle/be aware of winter terms | * update grade not-z scripts to handle/be aware of winter terms | ||
* update system page for (new)www | * update system page for (new)www | ||
- | * include information on db server | ||
- | * upgrade mail VM to jessie/ | ||
- | * upgrade LDAP VMs to jessie | ||
- | * create new router, using OpenBSD 5.7 | ||
* scripts to write: | * scripts to write: | ||
* user homedir backup pruning script | * user homedir backup pruning script | ||
Line 82: | Line 78: | ||
* https:// | * https:// | ||
* http:// | * http:// | ||
+ | * rxvt / .Xresources | ||
+ | * http:// | ||
======Other Days====== | ======Other Days====== | ||
- | ======November 13th, 2015====== | ||
- | =====C++ Operator Overloading===== | ||
- | I remember this used to seem so confusing in the past... but having played so heavily with pointers, linked lists, and manipulations therein, this suddenly wasn't any bit of a problem at all. | ||
- | Working on code for a custom number class: | + | ======August 28th, 2022====== |
+ | =====dokuwiki included pages no edit button (fixed)===== | ||
+ | I wanted | ||
- | <code c++> | + | Unfortunately, |
- | number & number | + | |
- | { | + | |
- | this -> add(rhs); | + | |
- | return *this; | + | |
- | } | + | |
- | number & number :: operator=(const number &rhs) | + | <code php> |
- | { | + | function html_secedit($text, |
- | if (this != &rhs) // with equal, need to check for self-references | + | global $INFO; |
- | | + | |
- | | + | if((isset($INFO) && |
- | | + | |
+ | | ||
} | } | ||
- | | + | |
+ | | ||
+ | ' | ||
} | } | ||
</ | </ | ||
+ | ======March 12th, 2020====== | ||
+ | |||
+ | =====borked journal, maybe fix===== | ||
+ | |||
+ | < | ||
+ | tune2sf -O ^has_journal / | ||
+ | e2fsck -f / | ||
+ | tune2sf -j / | ||
+ | </ | ||
+ | |||
+ | Obtained from: | ||
+ | |||
+ | * https:// | ||
+ | ======November 21st, 2019====== | ||
+ | =====pi4b dual head===== | ||
+ | Apparently I was missing something when building up from the lite version of raspbian. For when I popped in a new raspbian (the full desktop version) everything came up just fine. | ||
+ | |||
+ | Oh well. At least things are now working as they should. | ||
+ | |||
+ | ======November 19th, 2019====== | ||
+ | =====pi4b dual head issues===== | ||
+ | Attempting to set up a fresh raspbian install on the pi4b. Strangely, getting issues with dual head: it is only coming up in mirrored mode (or when I play with it, not at all). | ||
+ | |||
+ | The only major variables that have changed: | ||
+ | |||
+ | * new raspbian release (I could test my old setup.. that is easy enough to verify) | ||
+ | * no longer using HDMI monitors, but the DVI connections on the LAIR monitors. | ||
+ | * further investigation suggests the pi may be seeing identical EDIDs and other monitor ID things, so it is defaulting to a mirroring mode. | ||
+ | * **tvservice -l** consistently identifies two displays, so the hardware sees it, the software is not. | ||
+ | |||
+ | Interestingly: | ||
+ | ======March 15th, 2018====== | ||
+ | Setting up the raspberry pi 3 for use in the comporg class. Named it **pi3b**, and will get the IP of 10.80.2.48; running the latest stable release of rasbian. | ||
+ | |||
+ | Looking to get LDAP and autofs going, then installing packages to make it minimally functional for our purposes. | ||
+ | |||
+ | ======March 6th, 2018====== | ||
+ | Aside from an attempt at restarting my status-reporting habits in January of 2017, I totally neglected it for the remainder of the year. | ||
+ | |||
+ | So here we go, attempting another go. Will we be successful? | ||
+ | |||
+ | =====pods configured for better SSD operation===== | ||
+ | In other recent projects, I encountered some useful configuration options to improve performance, | ||
+ | |||
+ | I ended up taking a Debian USB installer, booting each pod in rescue mode, getting to a prompt, and running the following on EACH: | ||
+ | |||
+ | <cli> | ||
+ | # umount / | ||
+ | # tune2fs -O ^has_journal /dev/sda1 | ||
+ | # tune2fs -o discard /dev/sda1 | ||
+ | </ | ||
+ | |||
+ | Then on the master nodes, I enhanced both **/ | ||
+ | |||
+ | < | ||
+ | # /etc/fstab: static file system information. | ||
+ | # | ||
+ | # <file system> <mount point> | ||
+ | / | ||
+ | tmpfs / | ||
+ | tmpfs / | ||
+ | tmpfs / | ||
+ | tmpfs / | ||
+ | </ | ||
+ | |||
+ | Note how I put the log files in RAM too (on the pods)... this should greatly reduce extraneous writes. | ||
+ | |||
+ | Then at the bottom of **/ | ||
+ | |||
+ | < | ||
+ | #!/bin/sh -e | ||
+ | # | ||
+ | # rc.local | ||
+ | # | ||
+ | IPADDR= | ||
+ | while [ -z " | ||
+ | IPADDR=`/ | ||
+ | sleep 1 | ||
+ | done | ||
+ | / | ||
+ | / | ||
+ | echo " | ||
+ | echo " | ||
+ | echo " | ||
+ | |||
+ | echo deadline > / | ||
+ | echo 1 > / | ||
+ | |||
+ | exit 0 | ||
+ | </ | ||
+ | |||
+ | As the **deadline** scheduler has frequent mention of usage with SSDs. | ||
+ | |||
+ | Useful URLs: | ||
+ | |||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | |||
+ | |||
+ | =====lab46too SSD updates===== | ||
+ | With the pods having seen their SSD updates, I am looking to do the same for lab46too, testing to make sure the similar changes can be applied to that machine before rolling them over to lab46 proper. | ||
+ | |||
+ | I've updated the /etc/fstab and / | ||
+ | |||
+ | I had to remove the commit=600 from the /home partition. For some reason it didn't want to mount with that. | ||
======Month Status Page Navigation====== | ======Month Status Page Navigation====== | ||
- | ^ [[haas/ | + | ^ [[haas/ |