Sun Fundamentals of Solaris 7 EU-118 Student Guide With Instructor Notes phần 9 doc

13 Setting Printer Job Options You can also set the time interval that the Print Manager uses to check the current print queue, as shown in the following illustration: Printing 13-15 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Printing From the File Manager You can print a file from the File Manager window by dragging and dropping it on the Print Manager icon or dropping the object directly into the Print Manager window Once the file object has been dropped into the Print Jobs window, another window will be displayed in which you can: q Designate an alternative printer to print the file q Designate the number of copies of the file to be printed q Set a banner title (which will be displayed in the Print Manager window alongside the print object) q Select specific pages to print q Designate which UNIX print command options should be used as an alternative to the default print command Once the Print button is selected, the file will be sent to the appropriate printer queue 13-16 Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Printing From the File Manager Printing 13-17 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Displaying the Banner Page Title When a banner page title has been entered for a print request, that text will be displayed in the Print Manager window The name of the user who submitted the print request will be displayed below the banner text 13-18 Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Canceling a Print Request To cancel a print request, you must first select the Print Manager display object corresponding to that print request Once the object has been selected, use the Selected ® Cancel menu options You will be asked to confirm that you want to have the print request cancelled, as shown in the following illustration Again, you can only cancel your own print requests Printing 13-19 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Canceling a Print Request If you attempt to cancel another user’s print job from the Print Manager, the print job will reappear in the printer queue 13-20 Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Exercise: Printing Files Exercise objective – In this exercise you will use the print commands learned in this module to print a file Tasks Complete or answer the following: Files can be printed by dragging a File Manager file object on to the Default Printer icon (on the Front Panel) or into the Printer Jobs window, true or false? _ Print requests can only be sent to the system default printer, true or false? _ Only the system administrator can cancel print requests, true or false? _ From the command line, what command would you use to see if a printer was accepting requests? _ An alternate printer can be designated from the command line, true or false? _ Using the lp command, print the dante file on the default printer From the command line, check the status of the previously sent print request Printing 13-21 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Exercise: Printing Files Exercise Summary Discussion – Take a few minutes to discuss what experiences, issues, or discoveries you had during the lab exercises  Manage the discussion here based on the time allowed for this module, which was given in the “About This Course” module If you find you not have time to spend on discussion, then just highlight the key concepts students should have learned from the lab exercise q  Ask students what their overall experiences with this exercise have been You might want to go over any trouble spots or especially confusing areas at this time q  13-22 Conclusions Have students articulate any conclusions they reached as a result of this exercise experience q  Interpretations Ask students to interpret what they observed during any aspects of this exercise q  Experiences Applications Explore with students how they might apply what they learned in this exercise to situations at their workplace Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Exercise: Printing Files Exercise Solutions Files can be printed by dragging a File Manager file object on to the Default Printer icon (on the Front Panel) or into the Printer Jobs window, true or false? True Print requests can only be sent to the system default printer, true or false? False; If other printers are available to your system, you can designate the printer for each print job Only the system administrator can cancel print requests, true or false? False; A user can cancel his or her own job From the command line, what command would you use to see if a printer was accepting requests? $ lpstat -a An alternate printer can be designated from the command line, true or false? True Using the lp command, print the dante file on the default printer lp dante From the command line, check the status of the previously sent print request lpstat Printing 13-23 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 13 Check Your Progress Before continuing on to the next module, check that you are able to accomplish or answer the following: u u Print using the Print Manager in CDE u Determine and change the default printer u Set print options u 13-24 Use command-line commands to print a file, check print queue status, and cancel a print request Demonstrate the major functions of the Print Manager Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Memory Paging A program on a Sun workstation can address up to Gbytes of memory A system is typically equipped with some number of Mbytes of RAM During the execution, a process is placed in RAM (cut in pages) and is swapped page by page in and out of RAM This process is called paging Swapping rarely takes place on systems with very large amounts of RAM, whereas paging frequently occurs and is a normal part of system operation System Processes and Memory Management 16-19 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Exercise: Manipulating System Processes Exercise objective – In this exercise, you will use the commands learned in this module to determine PID numbers, kill processes, and control jobs Tasks Complete the following steps: In a terminal window, issue the following command: $ cat -v /dev/zero Note – This command is being used to produce a continuously running command for demonstration purposes only For information on the /dev/zero file, see man zero Open another terminal window (shell) and use the ps command to identify the process ID of the cat command From the current window, kill the cat command using the cat command’s process ID From the current window, determine the PID of the window in which the cat command was running and kill that window Issue the following command in the background: $ sleep 500 & Using the jobs command, find the job number of the sleep command in step Bring the job to the foreground and then put it back in the background Kill the job running the sleep command 16-20 Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Exercise: Manipulating System Processes Workshop Labs Use what you have learned so far in this course to work through the following: Getting rid of core files that are taking up space on your hard drive is a common task that is useful to run in the background Issue a find command that will look for and remove core files starting at the root directory, and send error messages to /dev/null Have the process run in the background Next, bring the job to the foreground to check on its progress, then place it back in the background again This type of command can use up quite a bit of system resources; at this point, the response time of your machine is more important to you than removing the core files Stop the job; it will be resumed in a later exercise System Processes and Memory Management 16-21 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Exercise: Manipulating System Processes Exercise Summary Discussion – Take a few minutes to discuss what experiences, issues, or discoveries you had during the lab exercises  Manage the discussion here based on the time allowed for this module, which was given in the “About This Course” module If you find you not have time to spend on discussion, then just highlight the key concepts students should have learned from the lab exercise q  Ask students what their overall experiences with this exercise have been You might want to go over any trouble spots or especially confusing areas at this time q  16-22 Conclusions Have students articulate any conclusions they reached as a result of this exercise experience q  Interpretations Ask students to interpret what they observed during any aspects of this exercise q  Experiences Applications Explore with students how they might apply what they learned in this exercise to situations at their workplace Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Exercise: Manipulating System Processes Exercise Solutions Complete the following steps: In a terminal window, issue the following command: $ cat -v /dev/zero Open another terminal window (shell) and use the ps command to identify the process ID of the cat command $ ps -ef | grep cat From the current window, kill the cat command using the cat command’s process ID $ kill PID where PID is the process ID of the cat command From the current window, determine the PID of the window in which the cat command was running and kill that window Look at the PPID of the cat command: $ ps -ef | grep PPID then type $ kill -9 PID where PID is the PPID of cat Issue the following command in the background: $ sleep 500 & Using the jobs command, find the job number of the sleep command in step Bring the job to the foreground and then put it back in the background $ fg %1 ^Z $ bg %1 System Processes and Memory Management 16-23 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Exercise: Manipulating System Processes Exercise Solutions Kill the job running the sleep command $ kill %1 16-24 Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Check Your Progress Before continuing on to the next module, check that you are able to accomplish or answer the following: u Identify processes on your system using the ps command u Find a process using the pgrep command u Control processes using the jobs command u Terminate unwanted processes using the kill and pkill commands System Processes and Memory Management 16-25 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 16 Think Beyond What you currently when you need to stop a process? How will using kill change that? What might be the advantage of having daemon processes? What might you expect to see that would indicate you are running out of virtual memory? 16-26 Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D Network Basics 17 Objectives Upon completion of this module, you should be able to: q Describe the terms client-server and distributed processing q Open a session on a remote machine using telnet q Log in remotely to another machine on the network q Use ftp to get a file from a remote system q Identify users logged in on the local network q Describe the concept of naming services 17-1 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 17 Relevance  Present the following question to stimulate the students and get them thinking about the issues and topics presented in this module While they are not expected to know the answer to the question, the answer should be of interest to them and inspire them to learn the content presented in this module Discussion – What network features you use now? What you think would be the advantages of being connected to other users, or a central file server? Additional Resources Additional resources – The following reference can provide additional details on the topics discussed in this module: q Solaris User’s Guide, Part Number 802-6499  Important – This is a fundamentals class, basically aimed at end-users This module is intended as an introduction to network commands only It is strongly suggested that you not teach the system administration files used for networking here That topic is fully covered in the SA-287 course and not intended for this audience  Be sure you have a naming service running so the students can use the rlogin and rusers commands 17-2 Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 17 Client-Server Example Networking Environment Figure 17-1 shows a sample networking environment with workstations, a printer, and so on Figure 17-1 Example Solaris Networking Environment  You may want to explain to the students the difference between having access to a naming service and not having access to a naming service You cannot assume that students will have access when they go back to their working environment  If you are not running a naming service, the host name and IP address must be recognized by the remote system as being in the /etc/inet/hosts file  If the user does not have a home directory on the remote machine, the user is automatically placed in the root (/) directory Network Basics 17-3 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 17 Client-Server Distributed Processing Distributed processing enables access to remote systems for the purpose of sharing information and network resources It also enables communication with users on other systems Network A network is a connection that enables an exchange of information between machines Two types of networks are: q q 17-4 Local area network (LAN) – A network that covers a small area, usually less than a few thousand feet Wide area network (WAN) – A network that can span thousands of miles Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 17 Client-Server Host A host is a computer system on a network The local host is the machine on which the user is currently working A remote host is a system that is being accessed by a user from another system Server A server provides resources to one or more clients by means of a network Client A client is a machine that uses the services from one or more servers on a network Naming Services Sometimes it is useful to have a common user and group list for hosts on a network In such situations, a naming service can be implemented by the sytem administrator A naming service allows users to be recognized by all remote machines on the network If the system administrator on your network chooses not to use a naming service, you must have an account on a remote machine in order to log in to it Network Basics 17-5 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 17 Network Commands telnet telnet is an application that is part of the Solaris environment It utilizes Transmission Control Protocol/Internet Protocol (TCP/IP) to connect to another system The telnet server simulates a terminal in order to authorize a user to connect to a remote system and work in that environment When using telnet, you can: q q Alternate between the remote session and the local session q 17-6 Open a session on a remote machine Access machines that not run under the UNIX environment Fundamentals of Solaris Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D 17 Network Commands telnet The following is an example of using telnet to connect to a remote system called beach: $ telnet beach Trying 192.9.49.10 Connected to beach Escape character is ‘^]’ 4.2 BSD UNIX (beach) login: jdupont Password: Last login: Wed Jun 19:03:33 on console beach% (Enter commands) beach% exit Connection closed by foreign host $ The following is an example of using telnet to alternate between the remote session and a local session: $ telnet beach Trying 192.9.49.10 Connected to beach Escape character is ‘^]’ 4.2 BSD UNIX (beach) login: jdupont Password: Last login: Wed Jun 19:08:15 on console beach% ^] telnet> ! $ pwd /home/user2 $ exit beach% exit Connection closed by foreign host Network Basics 17-7 Copyright 1999 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 1999, Revision D ... 1 696 Jul Jul Oct Oct Oct Mar Mar 15 15 19 19 19 7 16: 47 16:48 199 8 199 8 199 8 09: 52 09: 53 feathers feathers_6 file1 file2 file3 fruit fruit2 Oct Oct Jul Jul Oct Mar Mar 19 19 15 15 19 7 199 8 199 8... 199 8 199 8 16:48 16: 47 199 8 09: 53 09: 52 file1 file3 feathers_6 feathers file2 fruit2 fruit Mar Mar Jul Jul Oct Oct Oct 7 15 15 19 19 19 09: 52 09: 53 16: 47 16:48 199 8 199 8 199 8 fruit fruit2 feathers... 13-16 Fundamentals of Solaris Copyright 199 9 Sun Microsystems, Inc All Rights Reserved Enterprise Services August 199 9, Revision D 13 Printing From the File Manager Printing 13- 17 Copyright 199 9 Sun