From jperez at snf.stanford.edu  Fri Apr  4 09:08:09 2003
From: jperez at snf.stanford.edu (Jeannie Perez)
Date: Fri, 04 Apr 2003 09:08:09 -0800
Subject: Neet to be hooked up to printer
Message-ID: <3E8DBBF9.D69D3C0@snf.stanford.edu>

I need to print many items from  my customers and scheduling training.
Is this at all possible?

Thanks,
--
Jeannie Perez
Stanford Nanofabrication Facility
CIS Room 146, Mail Code 4070
Stanford, CA  94305
(650) 723-7997
jperez at snf.stanford.edu




From tberg at snf.stanford.edu  Tue Apr  8 07:16:42 2003
From: tberg at snf.stanford.edu (Ted Berg)
Date: Tue, 08 Apr 2003 07:16:42 -0700
Subject: Comments on coral
Message-ID: <3E92D9C9.B0BCC224@snf.stanford.edu>

John, et al,
    I talked to Bill about having comments available on coral as are
problems ,shutdowns, is this possible? also it would be nice to be able
to print out the summary page or one of the sorts if we are going to be
doing status reports. ted



From mahnaz at snf.stanford.edu  Tue Apr  8 08:53:24 2003
From: mahnaz at snf.stanford.edu (Mahnaz)
Date: Tue, 08 Apr 2003 08:53:24 -0700
Subject: [Fwd: Track message returned by e-mail program]
Message-ID: <3E92F074.722B09E2@snf.stanford.edu>

Hi John,

Here is the email I got from a user who had issues with SVG. We did not
get the email from coral that system has been reported.

mahnaz

-------------- next part --------------
An embedded message was scrubbed...
From: "Peter Hey" <peterhey at attbi.com>
Subject: Track message returned by e-mail program
Date: Mon, 7 Apr 2003 20:08:10 -0700
Size: 2332
URL: <http://snf.stanford.edu/pipermail/computer/attachments/20030408/9c8ad525/attachment.mht>

From bmurray at snf.stanford.edu  Tue Apr  8 11:14:33 2003
From: bmurray at snf.stanford.edu (Bill Murray)
Date: Tue, 8 Apr 2003 11:14:33 -0700 (PDT)
Subject: Bartlett & Windows 98
Message-ID: <Pine.LNX.4.04.10304081111290.19379-100000@snf.stanford.edu>

John and Mike,

I set up Uli to print on bartlett.  Then, I attempted to set Paul Jarebek
up to print on bartlett.  I failed because I could not find a Windows 98
CD.  Do you know where I can find one?  Paul doesn't have one.  He says
McVittie set him up.

Bill




From mikebell at stanford.edu  Tue Apr 15 16:17:34 2003
From: mikebell at stanford.edu (Mike Bell)
Date: Tue, 15 Apr 2003 16:17:34 -0700
Subject: printing problems
References: <3E9C36EF.5F18BFF@snf.stanford.edu>
Message-ID: <3E9C930D.34613D9D@stanford.edu>

Ray,

I'm out this week, but I'll forward your message to computer at stanford.edu.
You may want to make sure that your password and logon are the same on your
machine as on Fuga.

Mike

Ray Seymour wrote:

> I cannot use shared printer and cannot get computers near me to allow me
>
> to sign in on the shared printer computer named Fuga. Please advise who
> I need to contact to get this looked into.
> Thanks
> Ray



From dcchu at stanford.edu  Wed Apr 16 11:27:42 2003
From: dcchu at stanford.edu (dcchu at stanford.edu)
Date: Wed, 16 Apr 2003 11:27:42 -0700
Subject: "dcchu" cannot log in coral, urgent!
Message-ID: <1050517662.3e9da09e5372a@webmail.stanford.edu>

Dear Sir,

Yesterday I found I could not start coral after I logged in sunray 
computers. And I can not remotely log in coral as well. So now I can do 
nothing in the lab and I am very anxious about this. Could you please 
help me out? Thank you very much.

Account "dcchu"
Dachen Chu.


From shott at snf.stanford.edu  Thu Apr 17 09:41:06 2003
From: shott at snf.stanford.edu (John Shott)
Date: Thu, 17 Apr 2003 09:41:06 -0700
Subject: "dcchu" cannot log in coral, urgent!
References: <1050517662.3e9da09e5372a@webmail.stanford.edu>
Message-ID: <3E9ED922.9F1C0218@snf.stanford.edu>

Dachen:

Things should be fixed now ... apparently your project/account changed as of
01-Apr-2003 to 1DEB636.  This appears to have been an account number that was
used way back in 1993 ... so it was in our database, but didn't have all of
the proper fields associated with it so when you tried to login, it failed.

It should be fixed now ...

Thanks,

John

p.s. Bill ... for reference, this what an ancient account that was in both the
project and account tables but didn't have a valid charges_to entry.  Because
it was a valid project, however, it didn't complain when Jane entered that as
his default project.  We should probably go through and purge some of those
projects and accounts that are in the database but without proper charges_to
entries.


From mahnaz at snf.stanford.edu  Thu Apr 24 15:52:06 2003
From: mahnaz at snf.stanford.edu (Mahnaz)
Date: Thu, 24 Apr 2003 15:52:06 -0700
Subject: [Fwd: failure notice]
Message-ID: <3EA86A96.BC9010C@snf.stanford.edu>

Hello

I am trying to send this email out but it keeps failing, not sure what
it it or what am I doing wrong?

mahnaz
-------------- next part --------------
An embedded message was scrubbed...
From: MAILER-DAEMON at snf.stanford.edu
Subject: failure notice
Date: 24 Apr 2003 22:10:22 -0000
Size: 2600
URL: <http://snf.stanford.edu/pipermail/computer/attachments/20030424/91e529c0/attachment.mht>

From bmurray at snf.stanford.edu  Mon Apr 28 23:05:19 2003
From: bmurray at snf.stanford.edu (Bill Murray)
Date: Mon, 28 Apr 2003 23:05:19 -0700 (PDT)
Subject: Rebooted Sunray
Message-ID: <Pine.LNX.4.04.10304282302200.21308-100000@snf.stanford.edu>

John and Mike,

The Coral clients kept dying on the sunray so I rebooted the machine at
about 7:00pm this evening.  Everything appears to be running fine now.

Bill



From bmurray at snf.stanford.edu  Wed Apr 30 10:31:20 2003
From: bmurray at snf.stanford.edu (Bill Murray)
Date: Wed, 30 Apr 2003 10:31:20 -0700 (PDT)
Subject: [GECOS] island report with upcoming issues (fwd)
Message-ID: <Pine.LNX.4.04.10304301030500.16582-100000@snf.stanford.edu>

Mike,

Are we using OpenSSH?

Bill

---------- Forwarded message ----------
Date: Wed, 30 Apr 2003 10:04:17 -0700
From: Joe Little <jlittle at cs.stanford.edu>
To: gecos at island.stanford.edu
Subject: [GECOS] island report with upcoming issues

http://island.stanford.edu/ 
modules.php?op=modload&name=News&file=article&sid=528

Today's article, linked to above, covers an HPUX issue, MySQL issues,  
and most importantly, an issue present in OpenSSH that likely will  
involve updates for all OpenSSH-enabled systems. The attack vector to  
OpenSSH ties into weak passwords, and such an attack would be overly  
noisy. However, I still recommend updating systems when an update is  
available from your vendor. A current workaround is presented as well.

_______________________________________________
GECOS mailing list
GECOS at island.stanford.edu
http://island.stanford.edu/mailman/listinfo/gecos



From michael.bell at stanford.edu  Wed Apr 30 12:20:33 2003
From: michael.bell at stanford.edu (Michael Bell)
Date: Wed, 30 Apr 2003 12:20:33 -0700
Subject: [GECOS] island report with upcoming issues (fwd)
In-Reply-To: <Pine.LNX.4.04.10304301030500.16582-100000@snf.stanford.edu>
Message-ID: <001f01c30f4d$92483510$ab00a8c0@reef>

Bill,

I originally installed regular SSH, but I haven't looked at it in quite
a while.

Mike

-----Original Message-----
From: Bill Murray [mailto:bmurray at snf.stanford.edu] 
Sent: Wednesday, April 30, 2003 10:31 AM
To: computer at snf.stanford.edu
Subject: [GECOS] island report with upcoming issues (fwd)

Mike,

Are we using OpenSSH?

Bill

---------- Forwarded message ----------
Date: Wed, 30 Apr 2003 10:04:17 -0700
From: Joe Little <jlittle at cs.stanford.edu>
To: gecos at island.stanford.edu
Subject: [GECOS] island report with upcoming issues

http://island.stanford.edu/ 
modules.php?op=modload&name=News&file=article&sid=528

Today's article, linked to above, covers an HPUX issue, MySQL issues,  
and most importantly, an issue present in OpenSSH that likely will  
involve updates for all OpenSSH-enabled systems. The attack vector to  
OpenSSH ties into weak passwords, and such an attack would be overly  
noisy. However, I still recommend updating systems when an update is  
available from your vendor. A current workaround is presented as well.

_______________________________________________
GECOS mailing list
GECOS at island.stanford.edu
http://island.stanford.edu/mailman/listinfo/gecos