\chapter{Services}

This section describes computer services that SIPB provides.

{\bf Note:} If you are reading this section in hopes of finding where
to report a problem someone is having right now, you will probably
have better luck if you look at /mit/info/who\_fixes\_what instead; it
lists both SIPB and non-SIPB services.

\fixme{I'm not so fond of the format of this document.  It seems more like
a list of mailing lists (with some description of what they cover)
than a list of SIPB services.}

\fixme{To be written:
\begin{itemize}
\item scanner
\item ftp
\item vmware
\item lnitp
\item whats and rolodex... actually, the sipb locker is its own
      documentation project
\end{itemize}
}

\section{SIPB Services List}

The SIPB services list is located in /afs/sipb/admin/text/service-list.tex.

At the time of this writing (4 Feb 2002), it hasn't been updated since
1999.  It lists SIPB computer services, where they run, and who
maintains them, in a concise table format.

Ideally, it should be in sync with this document.

\section{Usenet}

SIPB currently maintains several news server machines; these include
senator-bedfellow (aka news.mit.edu), bloom-beacon, and sipb-server-2.

News clients connect to news.mit.edu (senator-bedfellow) and read news
from there; this machine has about a dozen disks which currently spool
about 4 months of text groups.  Our external news feeds are handled by
bloom-beacon, which sends and receives news to and from the outside
world (and other on-campus news servers, including senator-bedfellow).
This machine stores news for only 8-10 hours due to the high volume of
the feeds.  A test news server, sipb-server-2, also exists in order to
test changes to the server software before upgrading the production
machines.

The \maillist{usenet} list is for maintenance of the news servers.

There are a lot of people on \maillist{usenet};
a few of them actually read and,
if appropriate, answer the mail that gets sent to it.

There is a separate list, \maillist{usenet-grunge}, that gets control messages
(messages creating and removing newsgroups); no one actually gets this
list in mail, but several people read the discuss meeting for it.

\subsection*{Discuss meetings:}

bloom-picayune.mit.edu:/usr/spool/discuss/usenet

\noindent charon.mit.edu:/usr/spool/discuss/usenet-grunge

\noindent bloom-picayune.mit.edu:/usr/spool/discuss/usenet-stats

This meeting archives status reports from senator-bedfellow, the news
server that newsreaders connect to.  Currently, it archives three status
reports each day: a report giving some statistics for the whole day,
a report giving various load indicators for each
fifteen-minute interval during the day,
and a report on the incoming and outgoing feeds on bloom-beacon,
the server that exchanges news with the rest of the world.

\noindent charon.mit.edu:/usr/spool/discuss/usenet-archive

This meeting is for permanent archives of usenet information.
Currently, it is used for just about nothing.  Some information is
archived in /afs/sipb.mit.edu/project/news/notes instead.


\section{Charon}

\maillist{charon-maintainers} is a list for people
who maintain services on charon.mit.edu.
Currently, these services include the web server, several discuss
meetings, one of the webster servers, the bitnet gateway, a gopher
server, mail, and SIPB member logins, and maybe a few I left out.
This is currently a low-volume list.
\fixme{The list of services is out of date.  Gopher?!}

The web server has its own mailing list; see "webmaster" below
(Section \ref{webm}).

\subsection*{Discuss meetings:}

bloom-beacon.mit.edu:/usr/spool/discuss/charon-maint

\section{RTFM}

\fixme{Update this section.  rtfm is currently penguin-lust, anyway.}

\maillist{rtfm-maintainers} is a list for people who maintain services on
bloom-picayune.mit.edu.  Currently, these services include the RTFM
services (archiving of periodic Usenet postings and access to these
archives via WAIS, ftp, and a mail server), irc, ...

\subsection*{Discuss meetings:}

charon.mit.edu:/usr/spool/discuss/rtfm-maint

\section{Linux}

\fixme{Someone should update this.  alex\_c?}

\maillist{linux-dev} is a list for development of the SIPB port of the Athena
environment to Linux, and also for other Linux-related matters
appropriate for the SIPB members active in supporting Linux.  This is
a medium-volume list.

\maillist{linux-help} is a list for users to send questions about Linux
to.  It's
primarily for questions about the Athena port, but other questions are
also reasonable.  Most questions to this list get answered fairly
quickly.  This is a pretty high-volume list.

\maillist{linux-announce} is a list for announcements about the Athena
port.  This is a public list; everyone who uses the Athena port or
wants to receive announcements about it can add themselves.  It is
expected to be a low-volume list.

\subsection*{Discuss meetings:}

charon.mit.edu:/usr/spool/discuss/linux-dev

\noindent charon.mit.edu:/usr/spool/discuss/linux-help

\noindent charon.mit.edu:/usr/spool/discuss/linux-athena

\section{SIPB, Outland lockers}

\maillist{bug-sipb} and \maillist{bug-outland} are for bug reports
about software in the sipb and outland lockers, respectively.  Most
bug reports sent to these lists get answered fairly quickly.
They are medium- to low-volume lists.

\subsection*{Discuss meetings:}

bloom-picayune.mit.edu:/usr/spool/discuss/bug-sipb

\noindent charon.mit.edu:/usr/spool/discuss/bug-outland


\section{Webmaster}\label{webm}

The \maillist{webmaster} list is for maintenance of the SIPB web
server.  It is a high-volume list, receiving mail from all over the
net.

\subsection*{Discuss meetings:}

charon.mit.edu:/usr/spool/discuss/webm

\section{sipb-gnu}

This list is for maintenance of the SIPB gnu locker
(/afs/sipb/project/gnu).  It is a low-volume list.
It is not archived.


\section{sipb-afsreq} 


This list is for maintenance of the SIPB AFS cell.  It is a low-volume
list.

\subsection*{Discuss meetings:}

bloom-picayune.mit.edu:/usr/spool/discuss/sipb-afsreq

\input{backup}

\input{webster}