conversations.from: human
conversations.value: a title for a book about Novell, Netherlands, European with the genre: Computers & Technology, Networking & Cloud Computing
conversations.from: assistant
conversations.value: A title for this book could be 'The Definitive Guide to SUSE Linux Enterprise Server'
conversations.from: human
conversations.value: Give me the first five paragraphs for this book.
conversations.from: assistant
conversations.value: The Definitive Guide to SUSE Linux Enterprise Server
  Whereas the ntpq -p command gives generic information, more detailed information can be obtained by using the ntpdc command. This command can be used as an interactive interface or as a command-line utility. You should note, however, that it only works on servers that haven't been configured to deny ntpdc commands, using the noquery restriction. Unfortunately, many NTP servers won't reveal much on ntpdc. You can also use ntpdc to get more information about the local time configuration. You can use, for example, the ntpdc -c loopinfo command, to display in seconds how far off the system time is, or ntpdc -c kerninfo, to display the current correction that still has to be applied to the local clock (see Listing 11-7).
  Use ntpdc -c loopinfo and ntpdc -c kerninfo to get more information about the current state of your clock.
  Once the local clock has been synchronized sufficiently, use hwclock --systohc to write the system time to the hardware clock.
  Even if hosted DNS servers are becoming more and more common, SUSE offers great options to configure your own internal DNS server. All types of DNS are supported: DNS master servers, DNS slave servers, and Cache-only servers. As, in setting up DNS, many configuration files relate to one another, it makes sense to set up a base DNS configuration with YaST, after which you can manually modify the related configuration files.
  To set up DNS with YaST, select Network Services ➤ DNS Server. This will start the bind packages for you, after which the configuration of DNS can be started. Next, you'll go through a wizard to complete all steps of the DNS configuration. In the first screen of this wizard (see Figure 11-5), you can configure a forwarder.
conversations.from: human
conversations.value: Give me five more paragraphs.
conversations.from: assistant
conversations.value: When looking at the output of ps aux, you may notice that there are two different kinds of processes. The name of some are between square brackets; the names of others are not. If the name of a process is between square brackets, the process is part of the kernel. All other processes are "normal" processes.
  If you need more information about a process and what exactly it is doing, there are two ways to get that information. First, you can check the /proc directory for the particular process, for example, /proc/5658 gives information for the process with PID 5658. In this directory, you'll find the maps file that gives some more insight into how memory is mapped for this process. As you can see in Listing 15-11, this information is rather detailed. It includes the exact memory addresses this process is using and even tells you about subroutines and libraries that are related to this process.
  Listing 15-11. The /proc/PID/maps File Gives Detailed Information on Memory Utilization of Particular Processes
  The pmap command also shows what a process is doing. It gets its information from the /proc/PID/maps file. One of the advantages of the pmap command is that it gives detailed information about the order in which a process does its work. You can see calls to external libraries, as well as additional memory allocation (malloc) requests that the program is doing, as reflected in the lines that have [anon] at the end.
  One of the hardest things to do properly is the monitoring of storage utilization. The reason is that the storage channel typically is at the end of the chain. Other elements in your server can have a positive as well as a negative influence on storage performance. For example, if your server is low on memory, that will be reflected in storage performance, because if you don't have enough memory, there can't be a lot of cache and buffers, and thus, your server has more work to do on the storage channel.
conversations.from: human
conversations.value: Swap the first and the last sentence.
conversations.from: assistant
conversations.value: For example, if your server is low on memory, that will be reflected in storage performance, because if you don't have enough memory, there can't be a lot of cache and buffers, and thus, your server has more work to do on the storage channel. The name of some are between square brackets; the names of others are not. If the name of a process is between square brackets, the process is part of the kernel. All other processes are "normal" processes.
  If you need more information about a process and what exactly it is doing, there are two ways to get that information. First, you can check the /proc directory for the particular process, for example, /proc/5658 gives information for the process with PID 5658. In this directory, you'll find the maps file that gives some more insight into how memory is mapped for this process. As you can see in Listing 15-11, this information is rather detailed. It includes the exact memory addresses this process is using and even tells you about subroutines and libraries that are related to this process.
  Listing 15-11. The /proc/PID/maps File Gives Detailed Information on Memory Utilization of Particular Processes
  The pmap command also shows what a process is doing. It gets its information from the /proc/PID/maps file. One of the advantages of the pmap command is that it gives detailed information about the order in which a process does its work. You can see calls to external libraries, as well as additional memory allocation (malloc) requests that the program is doing, as reflected in the lines that have [anon] at the end.
  One of the hardest things to do properly is the monitoring of storage utilization. The reason is that the storage channel typically is at the end of the chain. Other elements in your server can have a positive as well as a negative influence on storage performance.When looking at the output of ps aux, you may notice that there are two different kinds of processes.
conversations.from: human
conversations.value: Give me the last four paragraphs.
conversations.from: assistant
conversations.value: To set up SUSE Manager Proxy, you'll first register the proxy to the SUSE Manager Server. To do that, you'll need a specific activation key for the proxy, as well as a bootstrap script. Next, you can run the bootstrap script on the proxy server, which will enter it in the registered systems overview in SUSE Manager. At this point, you can copy over the SUSE Manager certificates and keys from the SUSE Manager Server /root/ssl-build directory to /root/ssl-build on the proxy server. That allows you to run the proxy configuration script, which makes the proxy server operational. When that has happened, you can start registering client systems with the proxy.
  In a large environment, you may also benefit from using organizations in SUSE Manager. By default, you'll have only one organization, but it's possible to create multiple child organizations. Administration of child organizations can be delegated to other users (who, of course, must be created from the SUSE Manager interface).
  Creating an organization is not difficult. From the SUSE Manager web interface, under Admin ➤ Organizations, you'll create the organization. Next, you have to add SUSE Manager entitlements, as well as software entitlements, to the organization. Once this is done, you can create activation keys and corresponding bootstrap scripts, to start registering systems at the organization.
  In this chapter, you have learned how to configure SUSE Manager. You have worked your way through the different kinds of functionality that are offered by SUSE Manager and have read how to use it to manage software, monitor systems, and much more.
conversations.from: human
conversations.value: Add another sentence about assigned.
conversations.from: assistant
conversations.value: To set up SUSE Manager Proxy, you'll first register the proxy to the SUSE Manager Server. To do that, you'll need a specific activation key for the proxy, as well as a bootstrap script. Next, you can run the bootstrap script on the proxy server, which will enter it in the registered systems overview in SUSE Manager. At this point, you can copy over the SUSE Manager certificates and keys from the SUSE Manager Server /root/ssl-build directory to /root/ssl-build on the proxy server. That allows you to run the proxy configuration script, which makes the proxy server operational. When that has happened, you can start registering client systems with the proxy. 
  In a large environment, you may also benefit from using organizations in SUSE Manager. By default, you'll have only one organization, but it's possible to create multiple child organizations. The software and system entitlement for your company are assigned to the base organization, and the child organizations will inherit them. Administration of child organizations can be delegated to other users (who, of course, must be created from the SUSE Manager interface). 
  Creating an organization is not difficult. From the SUSE Manager web interface, under Admin ➤ Organizations, you'll create the organization. Next, you have to add SUSE Manager entitlements, as well as software entitlements, to the organization. Once this is done, you can create activation keys and corresponding bootstrap scripts, to start registering systems at the organization. 
  In this chapter, you have learned how to configure SUSE Manager. You have worked your way through the different kinds of functionality that are offered by SUSE Manager and have read how to use it to manage software, monitor systems, and much more.