Differences between current version and previous revision of CommitteeMeetingTopics.2006-10-16.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 6 | Last edited on Tuesday, October 17, 2006 1:35:22 pm | by IanMcDonald | |
| Older page: | version 5 | Last edited on Monday, October 16, 2006 11:25:59 pm | by BruceKingsbury | Revert |
@@ -16,9 +16,9 @@
__3. Correspondence__
Bank statement; forwarded to James.
-Account from Orcon for callout charge; Lindsay will clarify what the arrangement with Orcon is supposed to be, and perhaps invesitigate
other options for hosting.
+Account from Orcon for callout charge; Lindsay will clarify what the arrangement with Orcon is supposed to be, and perhaps investigate
other options for hosting.
__4. Treasurers report__
We currently have $1500 in the bank and $100 petty cash. Expecting more subs and regular payments from Google, so financially we're happy.
@@ -26,19 +26,19 @@
__5. Upcoming meetings__
1) Oct 30th; Plan9 presentation by PerryLorier.
- 2) Nov 27th Slackware
presentation by DeniseBates
+ 2) Nov 27th SlackWare
presentation by DeniseBates
- 3) Dec 9th End of year BBQ. James's house. BYO meat and drinks, WLUG to supply things like bread, salids, tables, BBQ.
+ 3) Dec 9th End of year [
BBQ]
. James's house. BYO meat and drinks, WLUG to supply things like bread, salids, tables, BBQ.
Future meetings, ideas required. Perhaps a presentation on iptables?
__6. WLUG servers__
One drive is near-death, a second is on the way out. Cost $110 ea. to replace. WLUG will purchase 2 replacement drives. Moved: Ian / James, Passed.
-We need to investigate redundency
, mirroring the functionality of each blade onto one or more other blades which can be enabled manually if any blade fails. We also need to look into systematic backups and some form of monitoring. And the current server setup needs to be properly documented. Ian to discuss these issues with Craig / Perry / John.
+We need to investigate redundancy
, mirroring the functionality of each blade onto one or more other blades which can be enabled manually if any blade fails. We also need to look into systematic backups and some form of monitoring. And the current server setup needs to be properly documented. Ian to discuss these issues with Craig / Perry / John.
__7. Life membership__
Posponed, to be discussed at a later meeting
