Also in the future CC [email protected], so everyone is aware of status on the machine. Ben
On Mar 22, 2016, at 1:01 PM, Allen, Benjamin S. <[email protected]> wrote:
nslcd segfaulted evidently, so the system wasn't aware of who you were. This machine isn't very stable. Note, at 1:30 I'm going to be work with Chris Knight to trial-and-error a kernel panic that LAMMPS can trigger.
Ben
On Mar 22, 2016, at 12:57 PM, Hal Finkel <[email protected]> wrote:
Hi Ben,
Thanks. When I tried to ssh to knl00 from ftlogin2, it prompted me for a password. How can I login?
-Hal
----- Original Message -----
From: "Benjamin S. Allen" <[email protected]> To: "Kalyan Kumaran" <[email protected]> Cc: "Hal J. Finkel" <[email protected]>, "James C. Osborn" <[email protected]> Sent: Monday, March 14, 2016 3:36:32 PM Subject: Re: [Alcf3-acceptance] Access to our KNL box
Added Hal.
Ben
On Mar 14, 2016, at 3:23 PM, Kumaran, Kalyan <[email protected]> wrote:
Hal, even though technically you are not part of theta acceptance you still have remote access to A0 hardware. So I’m fine with you accessing this system. Please note that we are keeping it as a top secret and not announcing beyond ALCF.
-Kumar
Begin forwarded message:
From: Kalyan Kumaran <[email protected]> Subject: Re: [Alcf3-acceptance] Access to our KNL box Date: March 14, 2016 at 12:43:07 PM CDT To: "[email protected]" <[email protected]> Cc: "Allen, Benjamin S." <[email protected]>
On Mar 14, 2016, at 12:41 PM, Kumaran, Kalyan <[email protected]> wrote:
We are ready to open up the KNL box to our staff preparing for Theta acceptance. If you would like access to the box please send an email to Ben with a cc to me. Please ask for access only if you are ready to run something and seriously test the machine. We need testers to find and report issues.
You will be added to the unix group and also the email list ([email protected]). We will use the mailing list for discussion and report issues.
Considering that this box is being shared by several users we will use a rather simplistic approach to scheduling. There is a file (/soft/scheduling/knl.txt) that will be used to announce a reservation or make one.
Example:
knl00 node status: in use by Scott Parker until 5pm or knl00 node status: free
and reservation requests like
Reservation: 3/17, 10am-2pm, Scott Parker
Each user of the node should update the file before and after every use
-Kumar
P.S.: we will be taking down the system sometime today to add a SSD.
_______________________________________________ Alcf3-acceptance mailing list [email protected] https://lists.alcf.anl.gov/mailman/listinfo/alcf3-acceptance
-- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne National Laboratory