[2256] in Enterprise Print Delivery Team
Re: followup to yesterday's meeting
daemon@ATHENA.MIT.EDU (Rocklyn E. Clarke)
Tue Feb 5 21:16:10 2002
Mime-Version: 1.0
Message-Id: <p05010407b886394ea35e@[18.152.2.129]>
In-Reply-To: <200201102147.QAA17130@brad-majors.mit.edu>
Date: Tue, 5 Feb 2002 21:16:04 -0500
To: Garry Zacheiss <zacheiss@MIT.EDU>
From: "Rocklyn E. Clarke" <rclarke@MIT.EDU>
Cc: Enterprise Printing Delivery Team <PRINTDEL@MIT.EDU>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hi Garry,
I hope you had a good time away from the Institute. I'm about to
officially ask you to install and be responsible for some software
for us. The explanation follows:
Several months ago ASST and the Enterprise Printing Team met to
discuss how various pieces of the project should be handled. Based
on that agreement (which I unfortunately overlooked when you and I
met last month), the responsibility for installing applications like
LPRng lies with my team (EAST), at least until more resources are
allocated to the Service Process. Applications like zephyr and
update_server will likely be handled the same way.
What all of this means is that for the time being it is my job (not
Jody's or ASST's) to make sure that this software gets installed. As
you might guess, that's where you come in. I would like for you to
officially install the revised LPRng on plunder (now our test server)
and then eventually on pillage. I will be out of the office for the
rest of this week, so I would like to plan for this to be done next
week (i.e. the week of 2/11/2001) if possible.
The Enterprise Printing team has decided that the installation of
zephyr and update server should be done after the project wraps
(hopefully this month). I will therefore be in touch with you about
these two tasks sometime in March (assuming we wrap on time).
The bigger picture here is that we want Athena Server Operations to
be responsible for maintaining these pieces of code (i.e. LPrng,
zephyr, update_server) on the test and production servers. We want
to keep our code in sync with the versions running on the Athena
Print Services servers. Hopefully this minimizes any maintenance
problems associated with this request. We're willing (this includes
EAST) to be trained to install various files and programs, but we
really need to have your team be responsible for the code itself and
any problems that arise with it. I think you already see yourself /
your team in this light, so I don't think I'm asking for anything
inappropriate. Nevertheless, I really would like to formalize this
understanding. Please let me know if you have any problems with
this. If our request is acceptable then I will email a summary to
Jonathon unless you would prefer to do so yourself.
Rocklyn
-------
At 4:47 PM -0500 1/10/02, Garry Zacheiss wrote:
> This message will be sort of long. Bear with me. I'll break
>this up into parts.
>
>I. zephyr.
>
> I built zephyr on pillage the other day. I haven't installed
>it since I figured that is something Jody can do. The build is in
>pillage:/home/zacheiss/zephyr/. Here's what you'll need to do:
>
> cp /home/zacheiss/zephyr/zhm/zgm /usr/local/sbin/zhm
> # arrange for /usr/local/sbin/zhm to be started at boot time.
> # It doesn't need any special arguments.
> # After it's started, run "zstat pillage" from an Athena
> # workstation to verify it's working.
> cp /home/zacheiss/zephyr/clients/zwrite/zwrite /usr/local/bin/zwrite
> # Add the line "zwrite=/usr/local/bin/zwrite" to /etc/lpd.conf
> # and restart lpd.
>
>Now, if clients request zephyr notification (Athena clients do by
>default) they should get it.
>
>II. update_server
>
> This is also built. It's sitting in
>pillage:/home/zacheiss/moira/update/. Someone will need to:
>
> cp /home/zacheiss/moira/update/update_server /usr/local/sbin/
> # arranfe for /usr/local/sbin/update_server to be started at
> # boot time.
> # It doesn't take any arguments and will background itself.
>
>III. Banner pages.
>
> This is the most complicated part. Printing of banner pages is
>controlled by the tag "bp" which can be put in /etc/lpd.conf or the
>printcap. I recommend putting it in /etc/lpd.conf. We have this in
>ours:
>
>bp=/usr/athena/libexec/filters/banner
>
>"bp" is supposed to point to a program that will generate a postscript
>banner page; it receives arguments in the same way filters do. See
>
>http://web.mit.edu/source/third/lprng/doc/LPRng-HOWTO-13.html
>
>for exhaustive documentation on that, if you haven't already.
>
>Now, for us, banner is the perl script that includes a variety of files:
>
>/usr/athena/lib/filters/banner.ps is the bulk of the postscript.
>
>/etc/athena/print.motd is just a text file that contains the text
>printed in the upper left hand corner of the banner page.
>
>/etc/athena/print.logo.ps is the image greyscaled over the motd. For
>us, this is just the Athena owl.
>
>(all of these pathnames are configured in the banner program, so you
>could change them to /usr/local/lib, or /etc, or whatever)
>
>I've put copies of all of these files in
>/mit/zacheiss/pickup/FOR_RCLARKE/.
>
>"banner" for us is just a perl script that defines some variables that
>are referenced by banner.ps, and then spits out the motd, logo, and
>banner. Starting from "banner", you should be able to have it put a
>mailing location somewhere on the page. I would suggest removing the
>logo and motd entirely and putting the location there, so you have both
>username and location in large letters of the header. You might find
>some other approach you prefer.
>
>Let me know if any of this is unclear.
>
>Garry
