Difference: AdrianPepperSandbox (1 vs. 14)

Revision 142010-11-08 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

Added:

>
>

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

-- AdrianPepper - 10 Oct 2006

Revision 132010-08-17 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

Line: 6 to 6

Created using my PDA.

Added:

>
>

<-- 

WebStatistics

r4590 - 2024-12-16 - 13:01
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XHier

r34 - 2024-12-16 - 11:39
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SolarisInstallation

r5 - 2024-11-01 - 14:33
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


News

r2 - 2024-10-30 - 12:05
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


ADAddUbuntuHardy

r4 - 2024-10-30 - 11:57
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SCSStandardUbuntu1604

r3 - 2024-10-30 - 11:55
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


NetworkTutorial5

r16 - 2024-10-30 - 09:56
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


ADUwCampus

r34 - 2024-10-30 - 09:14
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


MiscellaneousNotes

r94 - 2024-10-18 - 15:51
 MariHassanzada



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20231213

r2 - 2023-12-13 - 11:01
 ToddLichty



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20231129

r3 - 2023-11-29 - 11:32
 ToddLichty



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20231004

r5 - 2023-10-26 - 11:41
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20231010

NEW - 2023-10-10 - 16:54
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SATAccountsRequirements

r120 - 2023-09-11 - 14:37
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CSApplicationServerTalk

r6 - 2023-05-03 - 10:54
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


STComponentAccounts

r14 - 2022-10-26 - 11:30
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20220817

r2 - 2022-08-17 - 13:38
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20220811

r2 - 2022-08-11 - 10:48
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20220721

r2 - 2022-07-21 - 14:32
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20220616

r4 - 2022-06-16 - 23:47
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


Email

r63 - 2022-05-31 - 13:55
 TomCauduro



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20220427

r5 - 2022-04-27 - 12:00
 LawrenceFolland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20220420

r4 - 2022-04-20 - 10:58
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SATAccountsManagement

r4 - 2022-04-12 - 09:07
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeetingYYYYMMDD

r8 - 2022-04-01 - 12:22
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20220317

r7 - 2022-03-17 - 17:41
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SATAccountsUserStories

NEW - 2021-12-29 - 12:21
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20211201

r4 - 2021-12-13 - 10:54
 AnthonyBrennan



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20211124

r3 - 2021-11-25 - 11:12
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20211027

r6 - 2021-11-24 - 10:40
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20211123

r5 - 2021-11-23 - 16:35
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CSSaltStackWorkingGroup

r25 - 2021-11-22 - 12:14
 LawrenceFolland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20211118

r3 - 2021-11-18 - 14:36
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20211110

NEW - 2021-11-10 - 10:54
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20211102

r7 - 2021-11-04 - 14:48
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


FirewallZones

r4 - 2021-09-27 - 16:11
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210915

r3 - 2021-09-15 - 15:16
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SCSEmailPlans2021

r11 - 2021-09-14 - 11:07
 LawrenceFolland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeetingYYYYMMDD

r4 - 2021-09-01 - 14:08
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210901

r2 - 2021-09-01 - 14:07
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210901

r4 - 2021-09-01 - 11:29
 LawrenceFolland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210810

r2 - 2021-08-09 - 12:06
 AnthonyBrennan



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210727

r5 - 2021-07-27 - 12:17
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210720

r2 - 2021-07-20 - 11:38
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210112

r4 - 2021-07-20 - 10:57
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210713

r4 - 2021-07-13 - 15:55
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210707

r2 - 2021-07-07 - 15:02
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210629

NEW - 2021-06-29 - 11:20
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210623

NEW - 2021-06-22 - 11:39
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210622

NEW - 2021-06-22 - 10:24
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210615

r5 - 2021-06-15 - 17:21
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210518

r2 - 2021-05-18 - 11:42
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210512

r3 - 2021-05-12 - 16:04
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210428

NEW - 2021-04-28 - 15:45
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210427

r3 - 2021-04-28 - 10:51
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210420

r7 - 2021-04-28 - 08:56
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210511

r2 - 2021-04-27 - 11:53
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210330

r3 - 2021-04-27 - 10:20
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210413

NEW - 2021-03-30 - 10:40
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210331

NEW - 2021-03-17 - 15:04
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210317

r4 - 2021-03-17 - 14:59
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210309

r4 - 2021-03-09 - 17:29
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210309

r2 - 2021-03-09 - 12:15
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210224

r3 - 2021-03-09 - 10:55
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsDFScWgMeeting20210303

NEW - 2021-03-03 - 15:53
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210302

r2 - 2021-03-02 - 11:55
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


InventoryServiceMonitoring

r2 - 2021-02-18 - 12:41
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210210

r2 - 2021-02-11 - 15:54
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210202

r3 - 2021-02-11 - 15:37
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210209

r2 - 2021-02-09 - 13:08
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


LinuxWorkingGroupAgenda

r16 - 2021-02-09 - 10:40
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20210126

NEW - 2021-01-26 - 23:29
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsSaltStackWgMeeting20210120

NEW - 2021-01-20 - 12:56
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


TermGoalsSpring2017

r14 - 2020-12-21 - 10:44
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20201215

NEW - 2020-12-15 - 11:53
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


DfscProjectCharter

NEW - 2020-12-14 - 11:27
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


PlanningDirections

r33 - 2020-11-19 - 12:05
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


STToRTInvestigationChangeRequests

r17 - 2019-01-08 - 11:00
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


STToRTRequestsAndIssues

r34 - 2018-10-31 - 21:12
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


Stratum1NTPRpi

r15 - 2018-10-24 - 17:25
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CSCFWebsiteToWCMS

r2 - 2018-09-11 - 11:32
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


HostNamingRules

r6 - 2018-06-08 - 14:55
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SecureWeb-basedFile-sharingSystem-backingStorage

r31 - 2018-04-27 - 23:36
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


InventorySaltIntegration

NEW - 2017-08-23 - 17:14
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


AffObjectCodes

r5 - 2017-01-20 - 16:15
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


FileShareDFSProject20160928

NEW - 2016-10-16 - 23:15
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


FileShareDFSProject20160908

NEW - 2016-09-08 - 23:29
 LoriPaniak



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnterpriseMysqlClusterProject

r19 - 2016-04-11 - 17:47
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnterpriseMysqlClusterProject20160411

r3 - 2016-04-11 - 16:23
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnterpriseMysqlClusterProject20160331

r3 - 2016-04-08 - 13:06
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnterpriseMysqlClusterProject20160217

r5 - 2016-02-19 - 16:45
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnterpriseMysqlClusterProject20160120

r4 - 2016-02-17 - 14:15
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnterpriseMysqlClusterProject20160203

r6 - 2016-02-17 - 14:14
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnterpriseMysqlClusterProject20160211

r2 - 2016-02-17 - 14:13
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


EnvironmentComputingStudent

r12 - 2015-09-28 - 14:41
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


NotesOnw81u1404-sabertooth-2TB-s15-v3-

NEW - 2015-06-30 - 15:47
 MikeGore



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


UbuntuInstallSteps

r12 - 2014-09-19 - 13:24
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


LxcStart

r4 - 2014-08-07 - 11:32
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


NetworkSchema

r23 - 2014-07-31 - 17:28
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20040820

r3 - 2013-08-16 - 14:42
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


1799-1

r3 - 2013-08-15 - 10:46
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XhierOneZeroOne31May2005

r5 - 2013-08-14 - 11:23
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


WorkingGroup

r6 - 2013-08-08 - 11:33
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


UbuntuNinedotZeroFourDesktop

r2 - 2013-08-08 - 10:49
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SerialATA

r2 - 2013-08-01 - 11:36
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


IssuesWithKernel26

r10 - 2013-08-01 - 11:36
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


DavesBlackberryExperiments

r3 - 2013-07-30 - 15:53
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


HPProcurveSwitches

r40 - 2013-03-27 - 13:09
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XhierOneZeroOne16May2005

r8 - 2013-02-22 - 12:33
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20080602

r3 - 2013-02-11 - 10:36
 DrewPilcher



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


USGConfigMgmt

r5 - 2012-12-07 - 10:38
 TrevorGrove



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


WatFormMeeting20041005

r3 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


WatFormMeeting20041213

r3 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20061023

NEW - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


InventoryRedesignRequirementsDataModelNotes

r2 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


MirrorDotCS

r38 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20100129

r4 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


InventoryRedesignRequirements

r26 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20100226

r4 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CfiNo2004Clusters

r19 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


USGMacLabMC3003

r4 - 2012-09-06 - 11:50
 BillInce



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SponsorsDataEditingMistakes

r3 - 2012-07-31 - 12:08
 AdrianPepper



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XhierOneZeroOne07Mar2005

r6 - 2012-05-02 - 14:06
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


Ubuntu_LACP_Setup

r4 - 2011-03-18 - 11:32
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


NetworkTutorial11

r2 - 2010-11-18 - 11:10
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


NetworkHardware

r3 - 2010-09-14 - 17:02
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CycladesConfigurationProject

r11 - 2010-06-24 - 10:15
 LawrenceFolland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


UbuntuFirstImpressions

r8 - 2009-08-18 - 09:57
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20080718

NEW - 2008-07-18 - 15:25
 LawrenceFolland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


MirroringUbuntu

r14 - 2007-10-25 - 17:41
 WalterTautz



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


UbuntuInstalledSoftware

r2 - 2007-08-06 - 17:26
 DaveGawley



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


PrintingQueues

r13 - 2007-01-24 - 11:19
 WalterTautz



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XhierOneZeroOne07Jun2005

r4 - 2006-02-24 - 19:36
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XhierOneZeroOne21Feb2005

r6 - 2006-02-08 - 14:45
 IsaacMorland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XhierOneZeroOne28Feb2005

r3 - 2006-02-08 - 14:45
 IsaacMorland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20060112

r6 - 2006-01-12 - 14:56
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20050308

r6 - 2005-07-08 - 13:55
 LawrenceFolland



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


XhierOneZeroOne24May2005

r2 - 2005-05-31 - 13:38
 DanielAllen



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


SettingUpWatcher202

r2 - 2005-04-06 - 20:37
 MikePatterson



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->


CsLWGMeeting20050127

r4 - 2005-01-28 - 17:05
 MikePatterson



<--/twikiTopRow-->

<--/twikiSummary-->
<--/twikiBottomRow-->
<--/patternSearchResult-->
 -->

Try to delete pages by including a delete call...

Revision 122010-03-13 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

Line: 155 to 155

Deleted:

<
<

Man8Accounts-MasterSet_names

Line: 168 to 168

Deleted:

<
<

Leave the following for gxs for now...

CF.Man8Accounts-MasterSet_names

Added:

>
>

Leave the following for gxs for now...
(Note this is a page which does not call twikiman)

Man8Accounts-MasterSet_names

Leave the following for gxs for now...

CF.Man8Accounts-MasterSet_names

Set Url1 = https://www.cs.uwaterloo.ca/twiki/view/CF/ReadTheFineManPage?page=lc

<-- // Example of what we need to generate (for now) (minus !)
%INCLUDE{"http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=accounts-client§ion=8&package=accounts-master&host=cscf.cs.uwaterloo.ca"}%
 -->

<-- // Following can be seen in browser View Source for verification
%URLPARAM{"page"}% == 
%URLPARAM{"pagelist"}% == 
%URLPARAM{"section"}% == 
%URLPARAM{"package"}% == 
%URLPARAM{"host"}% == 
// The next peculiar "Set" line needs to be processed by twiki
//  but we don't want it in our output.
// Note variables should not be CF.WikiWords
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

Perhaps SponsorsDataAccountsDocumentationBig# or SponsorsDataAccountsDocumentationBig#_command

<-- 
 Set MANURL = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=&section=&package=&host=&pagelist=
  Set Bang = !
 
-->

<-- Uncomment following for debugging -->

<-- %MANURL% -->

%Bang%

<-- 
    Warning: Can't find topic CF.MANURL 
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

-- Man Page retrieval template page by AdrianPepper - 26 Feb 2010 / 19 Apr 2013

Changed:

<
<

Set Url2 = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=lc

Warning: Can't find topic TestNewSandbox.Url2

Set Url3 = https://www.cs.uwaterloo.ca/cscf/internal/request/Queue?q_status=Open&q_status=Stalled&q_status=recently+done&q_status=Closed&q_owner=&search=EXPR%3A+(id_other+!%3D+%22%22+AND+id_other+like+%22%25%23%25%22+)+AND+(date_created+%3E+(unix_timestamp()+-+864000))&q_columns=age&q_columns=last+acted&q_columns=Q&q_columns=!&q_columns=Urg&q_columns=%23&q_columns=Subject&q_columns=Req.&q_columns=Unit&q_columns=%3F&q_columns=Owner&q_columns=Status&q_reverse=1&q_sort=age&Submit=Search

Warning: Can't find topic TestNewSandbox.Url3

>
>

X * Set Url2 = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=lc

%INCLUDE{%Url2%}%

Deleted:

<
<

Set Url4 = https://www.cs.uwaterloo.ca/cscf/internal/request/Queue?q_status=Open&q_status=Stalled&q_status=recently+done&q_status=Closed&q_owner=&search=EXPR%%3A+(id_other+!%%3D+%%22%%22+AND+id_other+like+%%22%%25%%23%%25%%22+)+AND+(date_created+%%3E+(unix_timestamp()+-+864000))&q_columns=age&q_columns=last+acted&q_columns=Q&q_columns=!&q_columns=Urg&q_columns=%%23&q_columns=Subject&q_columns=Req.&q_columns=Unit&q_columns=%%3F&q_columns=Owner&q_columns=Status&q_reverse=1&q_sort=age&Submit=Search

Warning: Can't find topic TestNewSandbox.Url4

Set Url5 = http://www.cs.uwaterloo.ca/

Revision 112010-03-13 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

Line: 168 to 168

Added:

>
>

Leave the following for gxs for now...

Line: 178 to 181

Set Url1 = https://www.cs.uwaterloo.ca/twiki/view/CF/ReadTheFineManPage?page=lc

Changed:

<
<

Warning: This site does not allow %INCLUDE% of URLs

>
>

<-- // Example of what we need to generate (for now) (minus !)
%INCLUDE{"http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=accounts-client§ion=8&package=accounts-master&host=cscf.cs.uwaterloo.ca"}%
 -->

<-- // Following can be seen in browser View Source for verification
%URLPARAM{"page"}% == 
%URLPARAM{"pagelist"}% == 
%URLPARAM{"section"}% == 
%URLPARAM{"package"}% == 
%URLPARAM{"host"}% == 
// The next peculiar "Set" line needs to be processed by twiki
//  but we don't want it in our output.
// Note variables should not be CF.WikiWords
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

Perhaps SponsorsDataAccountsDocumentationBig# or SponsorsDataAccountsDocumentationBig#_command

<-- 
 Set MANURL = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=&section=&package=&host=&pagelist=
  Set Bang = !
 
-->

<-- Uncomment following for debugging -->

<-- %MANURL% -->

%Bang%

<-- 
    Warning: Can't find topic CF.MANURL 
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

-- Man Page retrieval template page by AdrianPepper - 26 Feb 2010 / 19 Apr 2013

Set Url2 = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=lc

Warning: Can't find topic TestNewSandbox.Url2

Revision 102010-03-11 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

Line: 205 to 205

Warning: Can't find topic Main.arpepper

Added:

>
>

Conclusion: https: is not recognized as a protocol.

Revision 92010-03-11 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

Line: 193 to 193

Set Url5 = http://www.cs.uwaterloo.ca/

%INCLUDE{!http://www.cs.uwaterloo.ca/}% did actually work

Added:

>
>

A restriction seems to be that included CGIs cannot come from same server as twiki runs on (ie. httpS://www.cs.uwaterloo.ca/

_Actually, it seems all https URLs will fail, although http ones work for some reason._

Set Url6a = htt
set Url6b = ps://www.cs.uwaterloo.ca/cscf/internal/request/DisplayRequest?serial_num=71533

Warning: This site does not allow %INCLUDE% of URLs

Warning: Can't find topic Main.arpepper

Revision 82010-03-05 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

Line: 80 to 80

Added:

>
>

Now make sure I've removed them all...

Wow, this first time I missed...

CF.Man8AccountsEdit_group

Note that if you correct the references before moving to Trash, they will be corrected to refer to Trash. That is, unless you uncheck the appropriate check box. So that's what you probably want to do.

Discovered via search a few I'd neglected to retain in my page...

Set Url1 = https://www.cs.uwaterloo.ca/twiki/view/CF/ReadTheFineManPage?page=lc

Revision 72010-03-04 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

Added:

>
>

http://www.google.com/search?hl=en&source=hp&q=lyrics+my+old+man+dustman

-- AdrianPepper - 10 Oct 2006

Created using my PDA.

Line: 7 to 9

Try to delete pages by including a delete call...

Added:

>
>

You cannot %INCLUDE% a delete call to delete pages, but at least you can make a menu of pages you want to delete...

E.g. Man5Accounts_devEquipment

https://www.cs.uwaterloo.ca/twiki/rename/CF/Man5Accounts_devEquipment?newweb=Trash&nonwikiword=on

Changed:

<
<

<-- -->

<-- Manpage converted by man2html 3.0.1 -->


Name:
	  sponsors - the accounts-master package's sponsor database



Synopsis:


Description:
	  The  sponsors  database  is  typically  stored  in a several
	  files, one per sponsor,  in  several  directories,  one  per
	  department.

	  Blank lines, and those beginning with a are ignored.

	  Lines  ending with a backslash, are considered to be contin-
	  ued on the following line as if it were  part  of  the  same
	  line.  (Ensure that the backslash really is the last charac-
	  ter on the line and is not followed by a space.)

	  In most cases the backslash isn't  required,  as  lines  may
	  also  be  continued by indenting the continuation lines with
	  tabs or spaces.

	  Lines beginning with an equal sign  separate  sections.	By
	  convention, eight equal signs (i.e. are used before each new
	  billcode or class, and  four  equal  signs  (i.e.  are  used
	  before each resource.

	  Each  line  comprises  a  keyword, immediately followed by a
	  colon, and a list of space-separated arguments.  Lists  must
	  never  be  empty.  If a particular keyword does not apply or
	  its value is unknown, the line should be  omitted  (or  com-
	  mented out with a and not left with an empty list.

	  If the first character of a list is a character, the rest of
	  the line will be the name of a decommentable file  (relative
	  to the current file if the first character of the name isn't
	  The line will then behave as if the list were  the  contents
	  of  that  file.	In  general this feature shouldn't be used
	  except where necessary to automate  the  processing  of  the
	  Registrar's data.



Structure:
	  The  data  is  stored  in  a logical hierarchy, each sponsor
	  being divided into several  billcodes,  each  billcode  into
	  several  classes,  and  each  class  into several resources.
	  Each billcode is assumed to  belong  to  the  most  recently
	  encountered  sponsor,  and resets all information associated
	  with any previously encountered billcodes.	Each  class  is
	  assumed to belong to the most recently encountered billcode,
	  and resets all information associated  with  any  previously
	  encountered  classes.  Each resource is assumed to belong to
	  the  most  recently  encountered  class,  and	resets	all
	  information	associated  with  any  previously  encountered
	  resource.

	  Values for each keyword are accumulated until an keyword  is
	  encountered,  at which point all accumulated data is applied
	  to the userids named on that line.



Sponsor Section:
	  This describes the person sponsoring everything that follows
	  to the end of the file.

	  Sponsor: Name of person

	  Department: Sponsor's UW department, if any

	  Address: Sponsor's paper mailing address, if any
			 Multiple lines may be used if required.

	  Email: Sponsor's e-mail address, if any

	  Billing: NoCharge
			 Sponsor is not charged for sponsored resources.

	  Billing: Automatic
			 Charges  are  automatically debited to sponsor's Finan-
			 cial Services account.

	  Statements: NoPaper
			 A paper statement is not mailed  to  the  sponsor  each
			 month.

	  Statements: NoWeb
			 The  sponsor's  monthly  statement is not posted in our
			 web space.

	  Infrastructure: FirstConnection

	  Userids: userid:idnumber list
			 Multiple lines  may  be  used  if  required.	See  the
			 Resource subsubsubsection for details about the Userids
			 list.



Billcode SubSection:
	  This defines the University billing code to which  all  fol-
	  lowing  classes, up to the end of the file or the next bill-
	  code, will be charged.  If  a  University  billcode  is  not
	  appropriate  (e.g.  resources  for internal use), some other
	  string may be used.  Check with the accountING package main-
	  tainer to see what is or is not appropriate.

	  Billcode: UW billcode or equivalent



Class SubSubSection:
	  This defines the the class to which all following resources,
	  up to the end of the file or the  next  class  or  billcode,
	  will be charged.

	  Class names must be unique (i.e. no class may have more than
	  one sponsor).  The reports produced by list_sponsors(8) will
	  begin on a new page for each class.

	  Class: Name of class
			 There  are  currently  no rules about what a class name
			 may be, but for the moment, to be consistent  with  the
			 old  software,  they should be of the form where is one
			 through five alphabetic characters,  is  three  digits,
			 and is zero or one alphabetic characters.

			 To  avoid  confusion  with  those classes automatically
			 generated from the Registrar's  data,  one  should  use
			 Dual-Case when creating new class names (e.g. Soft100).

	  Description: Description of class
			 A short description of the purpose of the class.

	  Usage: Primary use of the class
			 One of or The most significant value  is  as  it  means
			 that  usage  under  this  class should not count toward
			 active usage on a machine.  (e.g. for  a  staff  member
			 that must occasionally sign onto a researcher's machine
			 to maintain (but not use) its software.).

	  Subsidy: Dean's subsidy
			 or indicating whether or not the Dean's subsidy applies
			 to  resources  sponsored  by  this class (by default it
			 does).

	  Instructors: Name of professor, class instructor(s), et al.
			 The human(s) responsible for the class.

	  Enrollment: Number of members
			 The estimated size of the class.

	  Load: low, moderate, high, or heavy
			 The estimated cpu load for the class.

	  Requirements: Extra requirements
			 A short list of extra requirements (e.g. special  soft-
			 ware) for the class.

	  Fee: Lab fee
			 The  lab  fee charge for one term.  Can be given as the
			 number of cents, or suffixed with or The  two  keywords
			 may be abbreviated by truncation.

	  MembershipStarts: Date to start
			 Any  following  membership lists will be ignored before
			 this date.

	  MembershipEnds: Date to end
			 Any following membership lists will  be  ignored  after
			 this  date.  If a start date is given, the end date may
			 be expressed relatively (e.g.

	  Members:
			 A list of userids that belong to this class.  Note that
			 they  will not automatically be assigned any resources;
			 that must be done by giving a value to an trigger.



Resource SubSubSubSection:
	  This defines a set of resources to be billed to the  current
	  class  under  the  current billcode for the current sponsor.
	  The first line must select a resource:

	  Computing: List of host names
			 This defines resources  for  computer  accounts  to  be
			 billed  to the current class under the current billcode
			 for the current sponsor.

	  Printing: List of printer queue names
			 This defines printer access to be billed to the current
			 class  under the current billcode for the current spon-
			 sor.

	  MailAlias: mail-alias
			 This defines a mail alias (e.g.  to be  billed  to  the
			 current  class  under the current billcode for the cur-
			 rent sponsor.  If the mail-alias is more than 7 charac-
			 ters  long,  it  must  also  include square brackets to
			 indicate allowable userid truncation.
			 (e.g.  generates 5 aliases,
			 but generates only one alias).

	  PPP: List of PPP names
			 This defines PPP access to be  billed  to  the  current
			 class  under the current billcode for the current spon-
			 sor.

	  Any following lines define the  attributes  associated  with
	  the resource, which is allocated whenever a

	  AssignTo: List of userids

	  line  is encountered.  More than one line may be given for a
	  resource, typically either to avoid long lines or to apply a
	  start or end date to some but not all users.

	  The  special  userid  means  all  userids defined in members
	  lists for this class.

	  For the mailalias resource, the given  userids  may  contain
	  at-signs,  and  other punctuation, including colons, and are
	  not checked for validity.

	  Otherwise, each userid should be immediately followed by  an
	  optional  the redundancy providing checking for incorrect or
	  misspelled userids.  In addition, if the userid (and id num-
	  ber)  is  on  a machine not in the standard userid namespace
	  (e.g. for accessing our printers), it should be followed  by
	  indicating  the  name  of  another machine where the account
	  resides.

	  To avoid entering the id number each time  the  same  userid
	  appears  for  the same sponsor, the id number may be omitted
	  without generating any warnings if the userid and id  number
	  are given in the list in the Sponsor section.

	  If a

	  IgnoreUserids: List of userids

	  is  in effect when a userid list is encountered, any entries
	  common to both lists will be ignored.	(This  is  currently
	  implemented only for the resource.

	  The following attributes are common to most resources.

	  Quota: Restrictions on the amount of the resource
			 For  PPP accounts it is not defined, for printers it is
			 a money limit (format is as described in the  field  in
			 the  subsubsection above), and for computer accounts it
			 restricts the amount of  disk  space.	Disk  space  is
			 assumed  to  be  in kilobytes, but may be suffixed with
			 with or to indicate kilobytes, megabytes, or gigabytes.
			 To  specify  a  quota  without limit, the abbreviatable
			 keyword may be used.

	  SponsorshipStarts: Date sponsorship takes effect
			 This is a date before  which  the  sponsorship  of  the
			 resource does not apply.

	  SponsorshipEnds: Date sponsorship ends
			 This  is  a  date  after  which  the sponsorship of the
			 resource no longer applies.  If a start date is  given,
			 the  end  date  may  be expressed relatively (e.g.  End
			 dates are used, rather than simply deleting  the  data,
			 because  the sponsorship information may be required by
			 the accountING software for several  months  after  the
			 resources  are no longer needed.  For the PPP resource,
			 the end date may instead be given  as  the  name  of  a
			 host.  In that case, the sponsorship of the resource is
			 considered to have ended when the user no longer has an
			 account on the specified host.

	  Address: IP-Address
			 This applies only to the PPP resource.  This causes the
			 resource to be assigned this fixed  IP  address  rather
			 than being assigned one arbitrarily each time a connec-
			 tion is made.

	  Groups: Group membership
			 This applies only to the computing resource, and  lists
			 unix groups of which the user should be a member.

	  Hosts: List of hosts
			 This  applies only to the mailalias resource, and lists
			 unix regions on which the alias should apply.

	  Account: Sponsoring account
			 This applies only to the printing resource.  If  speci-
			 fied,  the  single  account  name  that  will  be  used
			 (instead of the class name) as the field in the printer
			 quota  database.	(i.e. the value the must be supplied
			 when using

			 Note that this means that these account  names  are  in
			 the  same namespace as class names, and therefore along
			 with the class names should be unique.



Second Attempt At A Descripton:
	  The following is meant to represent the  tree  structure  of
	  the database.

		  Each file contains one sponsor:

		  Sponsor:
		  Department:
		  Address:
		  Email:
		  Userids:

		  ======== Each sponsor is divided into one or more billcodes:

		  Billcode1		...		Billcode		...		BillcodeN

		  ======== Each billcode is divided into one or more classes:

				Class1		  ...		Class		  ...		ClassN
				Description1			  Description			  DescriptionN

		  ==== Each class is divided into one or more resources:

		  Computing...  Printing...  MailAlias...  PPP1...
		  Starts		  Starts		 Starts		  Starts
		  Ends			 Ends			Ends			 Ends
		  Quota			Quota		  Hosts			Address
		  Groups		  Account

		  Each resource is divided into one or more lists of userids:

				  AssignTo1	...	AssignTo2	...	AssignToN

	  Each sponsor, billcode, class, or resource section overrides
	  all attributes defined by  previous  sections  of  the  same
	  type.

	  Whenever  an  AssignTo  list  is  found  for a resource, all
	  attributes accumulated so far are assigned to each userid in
	  the list.

	  It  is  important  to  understand the difference between how
	  values are accumulated as described in the previous two sen-
	  tences.	The  Userid  list  does *not* reset any previously
	  defined values for the current resource.  So  for  instance,
	  if the file contained the sequence:

		  ...
		  Computing: math watdragon
		  Quota: 100M

		  AssignTo: *MEMBERS*

		  SponsorshipStarts: 1996/01/01
		  SponsorshipEnds: +1Year
		  AssignTo: jdoe jsmith

		  SponsorshipStarts: 1996/06/06
		  AssignTo: fbaggins gabandabalf

	  The  fbaggins account would also inherit the 100M quota and,
	  perhaps more surprisingly, the January 1997 end date.



Files Used:

See Also:
	  get_all_sponsors(3w), list_sponsors(8).



Copyright:
	  Copyright (C) 1995,2006, MFCF, University of Waterloo.

>
>

Now go hog-wild... In the page SponsorsDataAccountsDocumentationRaw I saved (in a comment) the names of the following 54 pages I had semi-automatically created. So the following list of "links" will semi-automatically delete them. (Move them to Trash

Changed:

<
<

<--

-->

>
>

Set Url1 = https://www.cs.uwaterloo.ca/twiki/view/CF/ReadTheFineManPage?page=lc

Line: 421 to 96

Set Url5 = http://www.cs.uwaterloo.ca/

Changed:

<
<

Warning: This site does not allow %INCLUDE% of URLs

>
>

! Warning: Can't find topic !http://www/cs/uwaterloo/ca.WebHome did actually work

Revision 62010-02-26 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

-- AdrianPepper - 10 Oct 2006

Created using my PDA.

Added:

>
>

Try to delete pages by including a delete call...

E.g. Man5Accounts_devEquipment

https://www.cs.uwaterloo.ca/twiki/rename/CF/Man5Accounts_devEquipment?newweb=Trash&nonwikiword=on

<-- -->

Line: 399 to 406

<--

-->

Changed:

<
<

<-- // Example of what we need to generate (for now) (minus !)
%INCLUDE{"http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=accounts-client§ion=8&package=accounts-master&host=cscf.cs.uwaterloo.ca"}%
 -->

<-- // Following can be seen in browser View Source for verification
%URLPARAM{"page"}% == 
%URLPARAM{"pagelist"}% == 
%URLPARAM{"section"}% == 
%URLPARAM{"package"}% == 
%URLPARAM{"host"}% == 
// The next peculiar "Set" line needs to be processed by twiki
//  but we don't want it in our output.
// Note variables should not be CF.WikiWords
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

Perhaps SponsorsDataAccountsDocumentationBig# or SponsorsDataAccountsDocumentationBig#_command

<-- 
 Set MANURL = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=&section=&package=&host=&pagelist=
  Set Bang = !
 
-->

<-- Uncomment following for debugging -->

<-- %MANURL% -->

%Bang%

<-- 
    Warning: Can't find topic CF.MANURL 
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

-- Man Page retrieval template page by AdrianPepper - 26 Feb 2010 / 19 Apr 2013

>
>

Set Url1 = https://www.cs.uwaterloo.ca/twiki/view/CF/ReadTheFineManPage?page=lc

Warning: This site does not allow %INCLUDE% of URLs

Set Url2 = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=lc

Warning: Can't find topic TestNewSandbox.Url2

Set Url3 = https://www.cs.uwaterloo.ca/cscf/internal/request/Queue?q_status=Open&q_status=Stalled&q_status=recently+done&q_status=Closed&q_owner=&search=EXPR%3A+(id_other+!%3D+%22%22+AND+id_other+like+%22%25%23%25%22+)+AND+(date_created+%3E+(unix_timestamp()+-+864000))&q_columns=age&q_columns=last+acted&q_columns=Q&q_columns=!&q_columns=Urg&q_columns=%23&q_columns=Subject&q_columns=Req.&q_columns=Unit&q_columns=%3F&q_columns=Owner&q_columns=Status&q_reverse=1&q_sort=age&Submit=Search

Warning: Can't find topic TestNewSandbox.Url3

Set Url4 = https://www.cs.uwaterloo.ca/cscf/internal/request/Queue?q_status=Open&q_status=Stalled&q_status=recently+done&q_status=Closed&q_owner=&search=EXPR%%3A+(id_other+!%%3D+%%22%%22+AND+id_other+like+%%22%%25%%23%%25%%22+)+AND+(date_created+%%3E+(unix_timestamp()+-+864000))&q_columns=age&q_columns=last+acted&q_columns=Q&q_columns=!&q_columns=Urg&q_columns=%%23&q_columns=Subject&q_columns=Req.&q_columns=Unit&q_columns=%%3F&q_columns=Owner&q_columns=Status&q_reverse=1&q_sort=age&Submit=Search

Warning: Can't find topic TestNewSandbox.Url4

Set Url5 = http://www.cs.uwaterloo.ca/

Warning: This site does not allow %INCLUDE% of URLs

Revision 52010-02-24 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

-- AdrianPepper - 10 Oct 2006

Line: 399 to 399

<--

-->

Changed:

<
<

Warning: Can't find topic TWiki.CF

>
>

<-- // Example of what we need to generate (for now) (minus !)
%INCLUDE{"http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=accounts-client§ion=8&package=accounts-master&host=cscf.cs.uwaterloo.ca"}%
 -->

<-- // Following can be seen in browser View Source for verification
%URLPARAM{"page"}% == 
%URLPARAM{"pagelist"}% == 
%URLPARAM{"section"}% == 
%URLPARAM{"package"}% == 
%URLPARAM{"host"}% == 
// The next peculiar "Set" line needs to be processed by twiki
//  but we don't want it in our output.
// Note variables should not be CF.WikiWords
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

Perhaps SponsorsDataAccountsDocumentationBig# or SponsorsDataAccountsDocumentationBig#_command

<-- 
 Set MANURL = http://www.cs.uwaterloo.ca/~arpepper/twikiman/twikiman?page=&section=&package=&host=&pagelist=
  Set Bang = !
 
-->

<-- Uncomment following for debugging -->

<-- %MANURL% -->

%Bang%

<-- 
    Warning: Can't find topic CF.MANURL 
 -->

This will probably never be made to work again. For now, you can look to see if the topic referenced is in SponsorsDataAccountsDocumentationBig.

-- Man Page retrieval template page by AdrianPepper - 26 Feb 2010 / 19 Apr 2013

Revision 42010-02-23 - AdrianPepper

Line: 1 to 1

META TOPICPARENT	name="Main.AdrianPepper"

-- AdrianPepper - 10 Oct 2006

Line: 399 to 399

<--

-->

Added:

>
>

Warning: Can't find topic TWiki.CF

Revision 32010-02-11 - AdrianPepper

  META TOPICPARENT 
 name="Main.AdrianPepper" 

-- AdrianPepper - 10 Oct 2006
- META TOPICPARENT
+ name="Main.AdrianPepper"
 <-- Manpage converted by man2html 3.0.1 -->
-<
<
+ Name:
->
>
+ Name:
 	  sponsors - the accounts-master package's sponsor database
-<
<
+ Synopsis:
->
>
+ Synopsis:
-<
<
+ Description:
->
>
+ Description:
 	  The  sponsors  database  is  typically  stored  in a several
	  files, one per sponsor,  in  several  directories,  one  per
	  department.
-<
<
+<-- Manpage converted by man2html 3.0.1 -->


 Name: 
	  sponsors - the accounts-master package's sponsor database



 Synopsis: 



 Description: 
	  The  sponsors  database  is  typically  stored  in a several
	  files, one per sponsor,  in  several  directories,  one  per
	  department.

	  Blank lines, and those beginning with a are ignored.

	  Lines  ending with a backslash, are considered to be contin-
	  ued on the following line as if it were  part  of  the  same
	  line.  (Ensure that the backslash really is the last charac-
	  ter on the line and is not followed by a space.)

	  In most cases the backslash isn't  required,  as  lines  may
	  also  be  continued by indenting the continuation lines with
	  tabs or spaces.

	  Lines beginning with an equal sign  separate  sections.	By
	  convention, eight equal signs (i.e. are used before each new
	  billcode or class, and  four  equal  signs  (i.e.  are  used
	  before each resource.

	  Each  line  comprises  a  keyword, immediately followed by a
	  colon, and a list of space-separated arguments.  Lists  must
	  never  be  empty.  If a particular keyword does not apply or
	  its value is unknown, the line should be  omitted  (or  com-
	  mented out with a and not left with an empty list.

	  If the first character of a list is a character, the rest of
	  the line will be the name of a decommentable file  (relative
	  to the current file if the first character of the name isn't
	  The line will then behave as if the list were  the  contents
	  of  that  file.	In  general this feature shouldn't be used
	  except where necessary to automate  the  processing  of  the
	  Registrar's data.



 Structure:
->
>
+ Structure:
 	  The  data  is  stored  in  a logical hierarchy, each sponsor
	  being divided into several  billcodes,  each  billcode  into
	  several  classes,  and  each  class  into several resources.
-<
<
+ Sponsor Section:
->
>
+ Sponsor Section:
 	  This describes the person sponsoring everything that follows
	  to the end of the file.
-<
<
+ Billcode SubSection:
->
>
+ Billcode SubSection:
 	  This defines the University billing code to which  all  fol-
	  lowing  classes, up to the end of the file or the next bill-
	  code, will be charged.  If  a  University  billcode  is  not
-<
<
+ Class SubSubSection:
->
>
+ Class SubSubSection:
 	  This defines the the class to which all following resources,
	  up to the end of the file or the  next  class  or  billcode,
	  will be charged.
-<
<
+ Resource SubSubSubSection:
->
>
+ Resource SubSubSubSection:
 	  This defines a set of resources to be billed to the  current
	  class  under  the  current billcode for the current sponsor.
	  The first line must select a resource:
 	  Quota: Restrictions on the amount of the resource
			 For  PPP accounts it is not defined, for printers it is
			 a money limit (format is as described in the  field  in
->
>
+			 the  subsubsection above), and for computer accounts it
 					restricts the amount of  disk  space.	Disk  space  is
			 assumed  to  be  in kilobytes, but may be suffixed with
			 with or to indicate kilobytes, megabytes, or gigabytes.
-<
<
+ Second Attempt At A Descripton:
->
>
+ Second Attempt At A Descripton:
 	  The following is meant to represent the  tree  structure  of
	  the database.
-<
<
+			 restricts the amount of  disk  space.	Disk  space  is
			 assumed  to  be  in kilobytes, but may be suffixed with
			 with or to indicate kilobytes, megabytes, or gigabytes.
			 To  specify  a  quota  without limit, the abbreviatable
			 keyword may be used.
-<
<
+	  SponsorshipStarts: Date sponsorship takes effect
			 This is a date before  which  the  sponsorship  of  the
			 resource does not apply.
->
>
+		  Each file contains one sponsor:
-<
<
+	  SponsorshipEnds: Date sponsorship ends
			 This  is  a  date  after  which  the sponsorship of the
			 resource no longer applies.  If a start date is  given,
			 the  end  date  may  be expressed relatively (e.g.  End
			 dates are used, rather than simply deleting  the  data,
			 because  the sponsorship information may be required by
			 the accountING software for several  months  after  the
			 resources  are no longer needed.  For the PPP resource,
			 the end date may instead be given  as  the  name  of  a
			 host.  In that case, the sponsorship of the resource is
			 considered to have ended when the user no longer has an
			 account on the specified host.
->
>
+		  Sponsor:
		  Department:
		  Address:
		  Email:
		  Userids:
-<
<
+	  Address: IP-Address
			 This applies only to the PPP resource.  This causes the
			 resource to be assigned this fixed  IP  address  rather
			 than being assigned one arbitrarily each time a connec-
			 tion is made.
->
>
+		  ==== Each sponsor is divided into one or more billcodes:
-<
<
+	  Groups: Group membership
			 This applies only to the computing resource, and  lists
			 unix groups of which the user should be a member.
->
>
+		  Billcode1		...		Billcode		...		BillcodeN
-<
<
+	  Hosts: List of hosts
			 This  applies only to the mailalias resource, and lists
			 unix regions on which the alias should apply.
->
>
+		  ==== Each billcode is divided into one or more classes:
-<
<
+	  Account: Sponsoring account
			 This applies only to the printing resource.  If  speci-
			 fied,  the  single  account  name  that  will  be  used
			 (instead of the class name) as the field in the printer
			 quota  database.	(i.e. the value the must be supplied
			 when using
->
>
+				Class1		  ...		Class		  ...		ClassN
				Description1			  Description			  DescriptionN
-<
<
+			 Note that this means that these account  names  are  in
			 the  same namespace as class names, and therefore along
			 with the class names should be unique.
->
>
+		  == Each class is divided into one or more resources:

		  Computing...  Printing...  MailAlias...  PPP1...
		  Starts		  Starts		 Starts		  Starts
		  Ends			 Ends			Ends			 Ends
		  Quota			Quota		  Hosts			Address
		  Groups		  Account

		  Each resource is divided into one or more lists of userids:

				  AssignTo1	...	AssignTo2	...	AssignToN

	  Each sponsor, billcode, class, or resource section overrides
	  all attributes defined by  previous  sections  of  the  same
	  type.

	  Whenever  an  AssignTo  list  is  found  for a resource, all
	  attributes accumulated so far are assigned to each userid in
	  the list.

	  It  is  important  to  understand the difference between how
	  values are accumulated as described in the previous two sen-
	  tences.	The  Userid  list  does not reset any previously
	  defined values for the current resource.  So  for  instance,
	  if the file contained the sequence:

		  ...
		  Computing: math watdragon
		  Quota: 100M

		  AssignTo: MEMBERS

		  SponsorshipStarts: 1996/01/01
		  SponsorshipEnds: +1Year
		  AssignTo: jdoe jsmith

		  SponsorshipStarts: 1996/06/06
		  AssignTo: fbaggins gabandabalf

	  The  fbaggins account would also inherit the 100M quota and,
	  perhaps more surprisingly, the January 1997 end date.
-<
<
+ Files Used:
->
>
+ Files Used:
-<
<
+ See Also:
->
>
+ See Also:
 	  get_all_sponsors(3w), list_sponsors(8).
-<
<
+ Copyright:
->
>
+ Copyright:
 	  Copyright (C) 1995,2006, MFCF, University of Waterloo.
-<
<
+Man(1) output converted with
man2html
 Revision 22010-02-11 - AdrianPepper

Line: 1 to 1
  


 META TOPICPARENT 
 name="Main.AdrianPepper" 

-- AdrianPepper - 10 Oct 2006

Created using my PDA.
Added: 
>
> <-- -->

<-- Manpage converted by man2html 3.0.1 -->


Name:
	  sponsors - the accounts-master package's sponsor database



Synopsis:



Description:
	  The  sponsors  database  is  typically  stored  in a several
	  files, one per sponsor,  in  several  directories,  one  per
	  department.

	  Blank lines, and those beginning with a are ignored.

	  Lines  ending with a backslash, are considered to be contin-
	  ued on the following line as if it were  part  of  the  same
	  line.  (Ensure that the backslash really is the last charac-
	  ter on the line and is not followed by a space.)

	  In most cases the backslash isn't  required,  as  lines  may
	  also  be  continued by indenting the continuation lines with
	  tabs or spaces.

	  Lines beginning with an equal sign  separate  sections.	By
	  convention, eight equal signs (i.e. are used before each new
	  billcode or class, and  four  equal  signs  (i.e.  are  used
	  before each resource.

	  Each  line  comprises  a  keyword, immediately followed by a
	  colon, and a list of space-separated arguments.  Lists  must
	  never  be  empty.  If a particular keyword does not apply or
	  its value is unknown, the line should be  omitted  (or  com-
	  mented out with a and not left with an empty list.

	  If the first character of a list is a character, the rest of
	  the line will be the name of a decommentable file  (relative
	  to the current file if the first character of the name isn't
	  The line will then behave as if the list were  the  contents
	  of  that  file.	In  general this feature shouldn't be used
	  except where necessary to automate  the  processing  of  the
	  Registrar's data.



<-- Manpage converted by man2html 3.0.1 -->


Name:
	  sponsors - the accounts-master package's sponsor database



Synopsis:



Description:
	  The  sponsors  database  is  typically  stored  in a several
	  files, one per sponsor,  in  several  directories,  one  per
	  department.

	  Blank lines, and those beginning with a are ignored.

	  Lines  ending with a backslash, are considered to be contin-
	  ued on the following line as if it were  part  of  the  same
	  line.  (Ensure that the backslash really is the last charac-
	  ter on the line and is not followed by a space.)

	  In most cases the backslash isn't  required,  as  lines  may
	  also  be  continued by indenting the continuation lines with
	  tabs or spaces.

	  Lines beginning with an equal sign  separate  sections.	By
	  convention, eight equal signs (i.e. are used before each new
	  billcode or class, and  four  equal  signs  (i.e.  are  used
	  before each resource.

	  Each  line  comprises  a  keyword, immediately followed by a
	  colon, and a list of space-separated arguments.  Lists  must
	  never  be  empty.  If a particular keyword does not apply or
	  its value is unknown, the line should be  omitted  (or  com-
	  mented out with a and not left with an empty list.

	  If the first character of a list is a character, the rest of
	  the line will be the name of a decommentable file  (relative
	  to the current file if the first character of the name isn't
	  The line will then behave as if the list were  the  contents
	  of  that  file.	In  general this feature shouldn't be used
	  except where necessary to automate  the  processing  of  the
	  Registrar's data.



Structure:
	  The  data  is  stored  in  a logical hierarchy, each sponsor
	  being divided into several  billcodes,  each  billcode  into
	  several  classes,  and  each  class  into several resources.
	  Each billcode is assumed to  belong  to  the  most  recently
	  encountered  sponsor,  and resets all information associated
	  with any previously encountered billcodes.	Each  class  is
	  assumed to belong to the most recently encountered billcode,
	  and resets all information associated  with  any  previously
	  encountered  classes.  Each resource is assumed to belong to
	  the  most  recently  encountered  class,  and	resets	all
	  information	associated  with  any  previously  encountered
	  resource.

	  Values for each keyword are accumulated until an keyword  is
	  encountered,  at which point all accumulated data is applied
	  to the userids named on that line.



Sponsor Section:
	  This describes the person sponsoring everything that follows
	  to the end of the file.

	  Sponsor: Name of person

	  Department: Sponsor's UW department, if any

	  Address: Sponsor's paper mailing address, if any
			 Multiple lines may be used if required.

	  Email: Sponsor's e-mail address, if any

	  Billing: NoCharge
			 Sponsor is not charged for sponsored resources.

	  Billing: Automatic
			 Charges  are  automatically debited to sponsor's Finan-
			 cial Services account.

	  Statements: NoPaper
			 A paper statement is not mailed  to  the  sponsor  each
			 month.

	  Statements: NoWeb
			 The  sponsor's  monthly  statement is not posted in our
			 web space.

	  Infrastructure: FirstConnection

	  Userids: userid:idnumber list
			 Multiple lines  may  be  used  if  required.	See  the
			 Resource subsubsubsection for details about the Userids
			 list.



Billcode SubSection:
	  This defines the University billing code to which  all  fol-
	  lowing  classes, up to the end of the file or the next bill-
	  code, will be charged.  If  a  University  billcode  is  not
	  appropriate  (e.g.  resources  for internal use), some other
	  string may be used.  Check with the accountING package main-
	  tainer to see what is or is not appropriate.

	  Billcode: UW billcode or equivalent



Class SubSubSection:
	  This defines the the class to which all following resources,
	  up to the end of the file or the  next  class  or  billcode,
	  will be charged.

	  Class names must be unique (i.e. no class may have more than
	  one sponsor).  The reports produced by list_sponsors(8) will
	  begin on a new page for each class.

	  Class: Name of class
			 There  are  currently  no rules about what a class name
			 may be, but for the moment, to be consistent  with  the
			 old  software,  they should be of the form where is one
			 through five alphabetic characters,  is  three  digits,
			 and is zero or one alphabetic characters.

			 To  avoid  confusion  with  those classes automatically
			 generated from the Registrar's  data,  one  should  use
			 Dual-Case when creating new class names (e.g. Soft100).

	  Description: Description of class
			 A short description of the purpose of the class.

	  Usage: Primary use of the class
			 One of or The most significant value  is  as  it  means
			 that  usage  under  this  class should not count toward
			 active usage on a machine.  (e.g. for  a  staff  member
			 that must occasionally sign onto a researcher's machine
			 to maintain (but not use) its software.).

	  Subsidy: Dean's subsidy
			 or indicating whether or not the Dean's subsidy applies
			 to  resources  sponsored  by  this class (by default it
			 does).

	  Instructors: Name of professor, class instructor(s), et al.
			 The human(s) responsible for the class.

	  Enrollment: Number of members
			 The estimated size of the class.

	  Load: low, moderate, high, or heavy
			 The estimated cpu load for the class.

	  Requirements: Extra requirements
			 A short list of extra requirements (e.g. special  soft-
			 ware) for the class.

	  Fee: Lab fee
			 The  lab  fee charge for one term.  Can be given as the
			 number of cents, or suffixed with or The  two  keywords
			 may be abbreviated by truncation.

	  MembershipStarts: Date to start
			 Any  following  membership lists will be ignored before
			 this date.

	  MembershipEnds: Date to end
			 Any following membership lists will  be  ignored  after
			 this  date.  If a start date is given, the end date may
			 be expressed relatively (e.g.

	  Members:
			 A list of userids that belong to this class.  Note that
			 they  will not automatically be assigned any resources;
			 that must be done by giving a value to an trigger.



Resource SubSubSubSection:
	  This defines a set of resources to be billed to the  current
	  class  under  the  current billcode for the current sponsor.
	  The first line must select a resource:

	  Computing: List of host names
			 This defines resources  for  computer  accounts  to  be
			 billed  to the current class under the current billcode
			 for the current sponsor.

	  Printing: List of printer queue names
			 This defines printer access to be billed to the current
			 class  under the current billcode for the current spon-
			 sor.

	  MailAlias: mail-alias
			 This defines a mail alias (e.g.  to be  billed  to  the
			 current  class  under the current billcode for the cur-
			 rent sponsor.  If the mail-alias is more than 7 charac-
			 ters  long,  it  must  also  include square brackets to
			 indicate allowable userid truncation.
			 (e.g.  generates 5 aliases,
			 but generates only one alias).

	  PPP: List of PPP names
			 This defines PPP access to be  billed  to  the  current
			 class  under the current billcode for the current spon-
			 sor.

	  Any following lines define the  attributes  associated  with
	  the resource, which is allocated whenever a

	  AssignTo: List of userids

	  line  is encountered.  More than one line may be given for a
	  resource, typically either to avoid long lines or to apply a
	  start or end date to some but not all users.

	  The  special  userid  means  all  userids defined in members
	  lists for this class.

	  For the mailalias resource, the given  userids  may  contain
	  at-signs,  and  other punctuation, including colons, and are
	  not checked for validity.

	  Otherwise, each userid should be immediately followed by  an
	  optional  the redundancy providing checking for incorrect or
	  misspelled userids.  In addition, if the userid (and id num-
	  ber)  is  on  a machine not in the standard userid namespace
	  (e.g. for accessing our printers), it should be followed  by
	  indicating  the  name  of  another machine where the account
	  resides.

	  To avoid entering the id number each time  the  same  userid
	  appears  for  the same sponsor, the id number may be omitted
	  without generating any warnings if the userid and id  number
	  are given in the list in the Sponsor section.

	  If a

	  IgnoreUserids: List of userids

	  is  in effect when a userid list is encountered, any entries
	  common to both lists will be ignored.	(This  is  currently
	  implemented only for the resource.

	  The following attributes are common to most resources.

	  Quota: Restrictions on the amount of the resource
			 For  PPP accounts it is not defined, for printers it is
			 a money limit (format is as described in the  field  in
					restricts the amount of  disk  space.	Disk  space  is
			 assumed  to  be  in kilobytes, but may be suffixed with
			 with or to indicate kilobytes, megabytes, or gigabytes.
			 To  specify  a  quota  without limit, the abbreviatable
			 keyword may be used.

	  SponsorshipStarts: Date sponsorship takes effect
			 This is a date before  which  the  sponsorship  of  the
			 resource does not apply.

	  SponsorshipEnds: Date sponsorship ends
			 This  is  a  date  after  which  the sponsorship of the
			 resource no longer applies.  If a start date is  given,
			 the  end  date  may  be expressed relatively (e.g.  End
			 dates are used, rather than simply deleting  the  data,
			 because  the sponsorship information may be required by
			 the accountING software for several  months  after  the
			 resources  are no longer needed.  For the PPP resource,
			 the end date may instead be given  as  the  name  of  a
			 host.  In that case, the sponsorship of the resource is
			 considered to have ended when the user no longer has an
			 account on the specified host.

	  Address: IP-Address
			 This applies only to the PPP resource.  This causes the
			 resource to be assigned this fixed  IP  address  rather
			 than being assigned one arbitrarily each time a connec-
			 tion is made.

	  Groups: Group membership
			 This applies only to the computing resource, and  lists
			 unix groups of which the user should be a member.

	  Hosts: List of hosts
			 This  applies only to the mailalias resource, and lists
			 unix regions on which the alias should apply.

	  Account: Sponsoring account
			 This applies only to the printing resource.  If  speci-
			 fied,  the  single  account  name  that  will  be  used
			 (instead of the class name) as the field in the printer
			 quota  database.	(i.e. the value the must be supplied
			 when using

			 Note that this means that these account  names  are  in
			 the  same namespace as class names, and therefore along
			 with the class names should be unique.



Second Attempt At A Descripton:
	  The following is meant to represent the  tree  structure  of
	  the database.
			 restricts the amount of  disk  space.	Disk  space  is
			 assumed  to  be  in kilobytes, but may be suffixed with
			 with or to indicate kilobytes, megabytes, or gigabytes.
			 To  specify  a  quota  without limit, the abbreviatable
			 keyword may be used.

	  SponsorshipStarts: Date sponsorship takes effect
			 This is a date before  which  the  sponsorship  of  the
			 resource does not apply.

	  SponsorshipEnds: Date sponsorship ends
			 This  is  a  date  after  which  the sponsorship of the
			 resource no longer applies.  If a start date is  given,
			 the  end  date  may  be expressed relatively (e.g.  End
			 dates are used, rather than simply deleting  the  data,
			 because  the sponsorship information may be required by
			 the accountING software for several  months  after  the
			 resources  are no longer needed.  For the PPP resource,
			 the end date may instead be given  as  the  name  of  a
			 host.  In that case, the sponsorship of the resource is
			 considered to have ended when the user no longer has an
			 account on the specified host.

	  Address: IP-Address
			 This applies only to the PPP resource.  This causes the
			 resource to be assigned this fixed  IP  address  rather
			 than being assigned one arbitrarily each time a connec-
			 tion is made.

	  Groups: Group membership
			 This applies only to the computing resource, and  lists
			 unix groups of which the user should be a member.

	  Hosts: List of hosts
			 This  applies only to the mailalias resource, and lists
			 unix regions on which the alias should apply.

	  Account: Sponsoring account
			 This applies only to the printing resource.  If  speci-
			 fied,  the  single  account  name  that  will  be  used
			 (instead of the class name) as the field in the printer
			 quota  database.	(i.e. the value the must be supplied
			 when using

			 Note that this means that these account  names  are  in
			 the  same namespace as class names, and therefore along
			 with the class names should be unique.



Files Used:

See Also:
	  get_all_sponsors(3w), list_sponsors(8).



Copyright:
	  Copyright (C) 1995,2006, MFCF, University of Waterloo.




Man(1) output converted with
man2html







<--
 -->
Revision 12006-10-10 - AdrianPepper

Line: 1 to 1
Added: 
>
> 


 META TOPICPARENT 
 name="Main.AdrianPepper" 

-- AdrianPepper - 10 Oct 2006

Created using my PDA.


View topic | History:  r14 < r13 < r12 < r11 | More topic actions...




 
  Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. 
 Ideas, requests, problems regarding TWiki? Send feedback
  META TOPICPARENT 
 name="Main.AdrianPepper" 

-- AdrianPepper - 10 Oct 2006

Created using my PDA.
- META TOPICPARENT
+ name="Main.AdrianPepper"
->
>
+<-- -->

<-- Manpage converted by man2html 3.0.1 -->


Name:
	  sponsors - the accounts-master package's sponsor database



Synopsis:



Description:
	  The  sponsors  database  is  typically  stored  in a several
	  files, one per sponsor,  in  several  directories,  one  per
	  department.

	  Blank lines, and those beginning with a are ignored.

	  Lines  ending with a backslash, are considered to be contin-
	  ued on the following line as if it were  part  of  the  same
	  line.  (Ensure that the backslash really is the last charac-
	  ter on the line and is not followed by a space.)

	  In most cases the backslash isn't  required,  as  lines  may
	  also  be  continued by indenting the continuation lines with
	  tabs or spaces.

	  Lines beginning with an equal sign  separate  sections.	By
	  convention, eight equal signs (i.e. are used before each new
	  billcode or class, and  four  equal  signs  (i.e.  are  used
	  before each resource.

	  Each  line  comprises  a  keyword, immediately followed by a
	  colon, and a list of space-separated arguments.  Lists  must
	  never  be  empty.  If a particular keyword does not apply or
	  its value is unknown, the line should be  omitted  (or  com-
	  mented out with a and not left with an empty list.

	  If the first character of a list is a character, the rest of
	  the line will be the name of a decommentable file  (relative
	  to the current file if the first character of the name isn't
	  The line will then behave as if the list were  the  contents
	  of  that  file.	In  general this feature shouldn't be used
	  except where necessary to automate  the  processing  of  the
	  Registrar's data.



<-- Manpage converted by man2html 3.0.1 -->


Name:
	  sponsors - the accounts-master package's sponsor database



Synopsis:



Description:
	  The  sponsors  database  is  typically  stored  in a several
	  files, one per sponsor,  in  several  directories,  one  per
	  department.

	  Blank lines, and those beginning with a are ignored.

	  Lines  ending with a backslash, are considered to be contin-
	  ued on the following line as if it were  part  of  the  same
	  line.  (Ensure that the backslash really is the last charac-
	  ter on the line and is not followed by a space.)

	  In most cases the backslash isn't  required,  as  lines  may
	  also  be  continued by indenting the continuation lines with
	  tabs or spaces.

	  Lines beginning with an equal sign  separate  sections.	By
	  convention, eight equal signs (i.e. are used before each new
	  billcode or class, and  four  equal  signs  (i.e.  are  used
	  before each resource.

	  Each  line  comprises  a  keyword, immediately followed by a
	  colon, and a list of space-separated arguments.  Lists  must
	  never  be  empty.  If a particular keyword does not apply or
	  its value is unknown, the line should be  omitted  (or  com-
	  mented out with a and not left with an empty list.

	  If the first character of a list is a character, the rest of
	  the line will be the name of a decommentable file  (relative
	  to the current file if the first character of the name isn't
	  The line will then behave as if the list were  the  contents
	  of  that  file.	In  general this feature shouldn't be used
	  except where necessary to automate  the  processing  of  the
	  Registrar's data.



Structure:
	  The  data  is  stored  in  a logical hierarchy, each sponsor
	  being divided into several  billcodes,  each  billcode  into
	  several  classes,  and  each  class  into several resources.
	  Each billcode is assumed to  belong  to  the  most  recently
	  encountered  sponsor,  and resets all information associated
	  with any previously encountered billcodes.	Each  class  is
	  assumed to belong to the most recently encountered billcode,
	  and resets all information associated  with  any  previously
	  encountered  classes.  Each resource is assumed to belong to
	  the  most  recently  encountered  class,  and	resets	all
	  information	associated  with  any  previously  encountered
	  resource.

	  Values for each keyword are accumulated until an keyword  is
	  encountered,  at which point all accumulated data is applied
	  to the userids named on that line.



Sponsor Section:
	  This describes the person sponsoring everything that follows
	  to the end of the file.

	  Sponsor: Name of person

	  Department: Sponsor's UW department, if any

	  Address: Sponsor's paper mailing address, if any
			 Multiple lines may be used if required.

	  Email: Sponsor's e-mail address, if any

	  Billing: NoCharge
			 Sponsor is not charged for sponsored resources.

	  Billing: Automatic
			 Charges  are  automatically debited to sponsor's Finan-
			 cial Services account.

	  Statements: NoPaper
			 A paper statement is not mailed  to  the  sponsor  each
			 month.

	  Statements: NoWeb
			 The  sponsor's  monthly  statement is not posted in our
			 web space.

	  Infrastructure: FirstConnection

	  Userids: userid:idnumber list
			 Multiple lines  may  be  used  if  required.	See  the
			 Resource subsubsubsection for details about the Userids
			 list.



Billcode SubSection:
	  This defines the University billing code to which  all  fol-
	  lowing  classes, up to the end of the file or the next bill-
	  code, will be charged.  If  a  University  billcode  is  not
	  appropriate  (e.g.  resources  for internal use), some other
	  string may be used.  Check with the accountING package main-
	  tainer to see what is or is not appropriate.

	  Billcode: UW billcode or equivalent



Class SubSubSection:
	  This defines the the class to which all following resources,
	  up to the end of the file or the  next  class  or  billcode,
	  will be charged.

	  Class names must be unique (i.e. no class may have more than
	  one sponsor).  The reports produced by list_sponsors(8) will
	  begin on a new page for each class.

	  Class: Name of class
			 There  are  currently  no rules about what a class name
			 may be, but for the moment, to be consistent  with  the
			 old  software,  they should be of the form where is one
			 through five alphabetic characters,  is  three  digits,
			 and is zero or one alphabetic characters.

			 To  avoid  confusion  with  those classes automatically
			 generated from the Registrar's  data,  one  should  use
			 Dual-Case when creating new class names (e.g. Soft100).

	  Description: Description of class
			 A short description of the purpose of the class.

	  Usage: Primary use of the class
			 One of or The most significant value  is  as  it  means
			 that  usage  under  this  class should not count toward
			 active usage on a machine.  (e.g. for  a  staff  member
			 that must occasionally sign onto a researcher's machine
			 to maintain (but not use) its software.).

	  Subsidy: Dean's subsidy
			 or indicating whether or not the Dean's subsidy applies
			 to  resources  sponsored  by  this class (by default it
			 does).

	  Instructors: Name of professor, class instructor(s), et al.
			 The human(s) responsible for the class.

	  Enrollment: Number of members
			 The estimated size of the class.

	  Load: low, moderate, high, or heavy
			 The estimated cpu load for the class.

	  Requirements: Extra requirements
			 A short list of extra requirements (e.g. special  soft-
			 ware) for the class.

	  Fee: Lab fee
			 The  lab  fee charge for one term.  Can be given as the
			 number of cents, or suffixed with or The  two  keywords
			 may be abbreviated by truncation.

	  MembershipStarts: Date to start
			 Any  following  membership lists will be ignored before
			 this date.

	  MembershipEnds: Date to end
			 Any following membership lists will  be  ignored  after
			 this  date.  If a start date is given, the end date may
			 be expressed relatively (e.g.

	  Members:
			 A list of userids that belong to this class.  Note that
			 they  will not automatically be assigned any resources;
			 that must be done by giving a value to an trigger.



Resource SubSubSubSection:
	  This defines a set of resources to be billed to the  current
	  class  under  the  current billcode for the current sponsor.
	  The first line must select a resource:

	  Computing: List of host names
			 This defines resources  for  computer  accounts  to  be
			 billed  to the current class under the current billcode
			 for the current sponsor.

	  Printing: List of printer queue names
			 This defines printer access to be billed to the current
			 class  under the current billcode for the current spon-
			 sor.

	  MailAlias: mail-alias
			 This defines a mail alias (e.g.  to be  billed  to  the
			 current  class  under the current billcode for the cur-
			 rent sponsor.  If the mail-alias is more than 7 charac-
			 ters  long,  it  must  also  include square brackets to
			 indicate allowable userid truncation.
			 (e.g.  generates 5 aliases,
			 but generates only one alias).

	  PPP: List of PPP names
			 This defines PPP access to be  billed  to  the  current
			 class  under the current billcode for the current spon-
			 sor.

	  Any following lines define the  attributes  associated  with
	  the resource, which is allocated whenever a

	  AssignTo: List of userids

	  line  is encountered.  More than one line may be given for a
	  resource, typically either to avoid long lines or to apply a
	  start or end date to some but not all users.

	  The  special  userid  means  all  userids defined in members
	  lists for this class.

	  For the mailalias resource, the given  userids  may  contain
	  at-signs,  and  other punctuation, including colons, and are
	  not checked for validity.

	  Otherwise, each userid should be immediately followed by  an
	  optional  the redundancy providing checking for incorrect or
	  misspelled userids.  In addition, if the userid (and id num-
	  ber)  is  on  a machine not in the standard userid namespace
	  (e.g. for accessing our printers), it should be followed  by
	  indicating  the  name  of  another machine where the account
	  resides.

	  To avoid entering the id number each time  the  same  userid
	  appears  for  the same sponsor, the id number may be omitted
	  without generating any warnings if the userid and id  number
	  are given in the list in the Sponsor section.

	  If a

	  IgnoreUserids: List of userids

	  is  in effect when a userid list is encountered, any entries
	  common to both lists will be ignored.	(This  is  currently
	  implemented only for the resource.

	  The following attributes are common to most resources.

	  Quota: Restrictions on the amount of the resource
			 For  PPP accounts it is not defined, for printers it is
			 a money limit (format is as described in the  field  in
					restricts the amount of  disk  space.	Disk  space  is
			 assumed  to  be  in kilobytes, but may be suffixed with
			 with or to indicate kilobytes, megabytes, or gigabytes.
			 To  specify  a  quota  without limit, the abbreviatable
			 keyword may be used.

	  SponsorshipStarts: Date sponsorship takes effect
			 This is a date before  which  the  sponsorship  of  the
			 resource does not apply.

	  SponsorshipEnds: Date sponsorship ends
			 This  is  a  date  after  which  the sponsorship of the
			 resource no longer applies.  If a start date is  given,
			 the  end  date  may  be expressed relatively (e.g.  End
			 dates are used, rather than simply deleting  the  data,
			 because  the sponsorship information may be required by
			 the accountING software for several  months  after  the
			 resources  are no longer needed.  For the PPP resource,
			 the end date may instead be given  as  the  name  of  a
			 host.  In that case, the sponsorship of the resource is
			 considered to have ended when the user no longer has an
			 account on the specified host.

	  Address: IP-Address
			 This applies only to the PPP resource.  This causes the
			 resource to be assigned this fixed  IP  address  rather
			 than being assigned one arbitrarily each time a connec-
			 tion is made.

	  Groups: Group membership
			 This applies only to the computing resource, and  lists
			 unix groups of which the user should be a member.

	  Hosts: List of hosts
			 This  applies only to the mailalias resource, and lists
			 unix regions on which the alias should apply.

	  Account: Sponsoring account
			 This applies only to the printing resource.  If  speci-
			 fied,  the  single  account  name  that  will  be  used
			 (instead of the class name) as the field in the printer
			 quota  database.	(i.e. the value the must be supplied
			 when using

			 Note that this means that these account  names  are  in
			 the  same namespace as class names, and therefore along
			 with the class names should be unique.



Second Attempt At A Descripton:
	  The following is meant to represent the  tree  structure  of
	  the database.
			 restricts the amount of  disk  space.	Disk  space  is
			 assumed  to  be  in kilobytes, but may be suffixed with
			 with or to indicate kilobytes, megabytes, or gigabytes.
			 To  specify  a  quota  without limit, the abbreviatable
			 keyword may be used.

	  SponsorshipStarts: Date sponsorship takes effect
			 This is a date before  which  the  sponsorship  of  the
			 resource does not apply.

	  SponsorshipEnds: Date sponsorship ends
			 This  is  a  date  after  which  the sponsorship of the
			 resource no longer applies.  If a start date is  given,
			 the  end  date  may  be expressed relatively (e.g.  End
			 dates are used, rather than simply deleting  the  data,
			 because  the sponsorship information may be required by
			 the accountING software for several  months  after  the
			 resources  are no longer needed.  For the PPP resource,
			 the end date may instead be given  as  the  name  of  a
			 host.  In that case, the sponsorship of the resource is
			 considered to have ended when the user no longer has an
			 account on the specified host.

	  Address: IP-Address
			 This applies only to the PPP resource.  This causes the
			 resource to be assigned this fixed  IP  address  rather
			 than being assigned one arbitrarily each time a connec-
			 tion is made.

	  Groups: Group membership
			 This applies only to the computing resource, and  lists
			 unix groups of which the user should be a member.

	  Hosts: List of hosts
			 This  applies only to the mailalias resource, and lists
			 unix regions on which the alias should apply.

	  Account: Sponsoring account
			 This applies only to the printing resource.  If  speci-
			 fied,  the  single  account  name  that  will  be  used
			 (instead of the class name) as the field in the printer
			 quota  database.	(i.e. the value the must be supplied
			 when using

			 Note that this means that these account  names  are  in
			 the  same namespace as class names, and therefore along
			 with the class names should be unique.



Files Used:

See Also:
	  get_all_sponsors(3w), list_sponsors(8).



Copyright:
	  Copyright (C) 1995,2006, MFCF, University of Waterloo.




Man(1) output converted with
man2html







<--
 -->
->
>
+ META TOPICPARENT 
 name="Main.AdrianPepper" 

-- AdrianPepper - 10 Oct 2006

Created using my PDA.
- META TOPICPARENT
+ name="Main.AdrianPepper"