mtpti5iD/redhat-docs_dataset huggingface dataset:
function::ctime Name function::ctime - Convert seconds since epoch into human readable date/time string. Synopsis Arguments epochsecs Number of seconds since epoch (as returned by gettimeofday_s ). General Syntax ctime:string(epochsecs:long) Description Takes an argument of seconds since the epoch as returned by gettimeofday_s . Returns a string of the form " Wed Jun 30 21:49:08 1993 " The string will always be exactly 24 characters. If the time would be unreasonable far in the past (before what can be represented with a 32 bit offset in seconds from the epoch) the returned string will be " a long, long time ago... " . If the time would be unreasonable far in the future the returned string will be " far far in the future... " (both these strings are also 24 characters wide). Note that the epoch (zero) corresponds to " Thu Jan 1 00:00:00 1970 " The earliest full date given by ctime, corresponding to epochsecs -2147483648 is " Fri Dec 13 20:45:52 1901 " . The latest full date given by ctime, corresponding to epochsecs 2147483647 is " Tue Jan 19 03:14:07 2038 " . The abbreviations for the days of the week are 'Sun', 'Mon', 'Tue', 'Wed', 'Thu', 'Fri', and 'Sat'. The abbreviations for the months are 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', and 'Dec'. Note that the real C library ctime function puts a newline ('\n') character at the end of the string that this function does not. Also note that since the kernel has no concept of timezones, the returned time is always in GMT.

Commands:
function ctime:string(epochsecs:long)
Chapter 24. Setting up a Remote Diskless System To set up a basic remote diskless system booted over PXE, you need the following packages: tftp-server xinetd dhcp syslinux dracut-network Note After installing the dracut-network package, add the following line to /etc/dracut.conf : Remote diskless system booting requires both a tftp service (provided by tftp-server ) and a DHCP service (provided by dhcp ). The tftp service is used to retrieve kernel image and initrd over the network via the PXE loader. Note SELinux is only supported over NFSv4.2. To use SELinux, NFS must be explicitly enabled in /etc/sysconfig/nfs by adding the line: RPCNFSDARGS="-V 4.2" Then, in /var/lib/tftpboot/pxelinux.cfg/default , change root=nfs:server-ip:/exported/root/directory to root=nfs:server-ip:/exported/root/directory,vers=4.2 . Finally, reboot the NFS server. The following sections outline the necessary procedures for deploying remote diskless systems in a network environment. Important Some RPM packages have started using file capabilities (such as setcap and getcap ). However, NFS does not currently support these so attempting to install or update any packages that use file capabilities will fail. 24.1. Configuring a tftp Service for Diskless Clients Prerequisites Install the necessary packages. See Chapter 24, Setting up a Remote Diskless System Procedure To configure tftp , perform the following steps: Procedure 24.1. To Configure tftp Enable PXE booting over the network: The tftp root directory ( chroot ) is located in /var/lib/tftpboot . Copy /usr/share/syslinux/pxelinux.0 to /var/lib/tftpboot/ : Create a pxelinux.cfg directory inside the tftp root directory: Configure firewall rules to allow tftp traffic. As tftp supports TCP wrappers, you can configure host access to tftp in the /etc/hosts.allow configuration file. For more information on configuring TCP wrappers and the /etc/hosts.allow configuration file, see the Red Hat Enterprise Linux 7 Security Guide . The hosts_access (5) also provides information about /etc/hosts.allow . Steps After configuring tftp for diskless clients, configure DHCP, NFS, and the exported file system accordingly. For instructions on configuring the DHCP, NFS, and the exported file system, see Section 24.2, "Configuring DHCP for Diskless Clients" and Section 24.3, "Configuring an Exported File System for Diskless Clients" .

Commands:
add_dracutmodules+=" nfs"
systemctl enable --now tftp
cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot/
mkdir -p /var/lib/tftpboot/pxelinux.cfg/
11.4. Setting up a Kerberos Client for Smart Cards Smart cards can be used with Kerberos, but it requires additional configuration to recognize the X.509 (SSL) user certificates on the smart cards: Install the required PKI/OpenSSL package, along with the other client packages: Edit the /etc/krb5.conf configuration file to add a parameter for the public key infrastructure (PKI) to the [realms] section of the configuration. The pkinit_anchors parameter sets the location of the CA certificate bundle file. Add the PKI module information to the PAM configuration for both smart card authentication ( /etc/pam.d/smartcard-auth ) and system authentication ( /etc/pam.d/system-auth ). The line to be added to both files is as follows: If the OpenSC module does not work as expected, use the module from the coolkey package: /usr/lib64/pkcs11/libcoolkeypk11.so . In this case, consider contacting Red Hat Technical Support or filing a Bugzilla report about the problem.

Commands:
yum install krb5-pkinit yum install krb5-workstation krb5-libs
[realms] EXAMPLE.COM = { kdc = kdc.example.com.:88 admin_server = kdc.example.com default_domain = example.com pkinit_anchors = FILE:/usr/local/example.com.crt }
auth optional pam_krb5.so use_first_pass no_subsequent_prompt preauth_options=X509_user_identity=PKCS11:/usr/lib64/pkcs11/opensc-pkcs11.so
7.172. python-nss 7.172.1. RHBA-2015:1324 - python-nss bug fix and enhancement update Updated python-nss packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The python-nss packages provide bindings for Network Security Services (NSS) that allow Python programs to use the NSS cryptographic libraries for SSL/TLS and PKI certificate management. Note The python-nss packages have been upgraded to upstream version 0.16.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1154776 ) Bug Fix BZ# 1154776 Added support for setting trust attributes on a certificate. * Added support for the SSL version range API, information on the SSL cipher suites, and information on the SSL connection. Users of python-nss are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ .NET in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To use AMQ .NET on Red Hat Enterprise Linux, you must install the the .NET Core 3.1 developer tools. For information, see the .NET Core 3.1 getting started guide . To build programs using AMQ .NET on Microsoft Windows, you must install Visual Studio. 2.2. Installing on Red Hat Enterprise Linux Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.8.0 .NET Core .zip file. Use the unzip command to extract the file contents into a directory of your choosing. USD unzip amq-clients-2.8.0-dotnet-core.zip When you extract the contents of the .zip file, a directory named amq-clients-2.8.0-dotnet-core is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document. Use a text editor to create the file USDHOME/.nuget/NuGet/NuGet.Config and add the following content: <?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3"/> <add key="amq-clients" value=" <install-dir> /nupkg"/> </packageSources> </configuration> If you already have a NuGet.Config file, add the amq-clients line to it. Alternatively, you can move the .nupkg file inside the <install-dir> /nupkg directory to an existing package source location. 2.3. Installing on Microsoft Windows Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.8.0 .NET .zip file. Extract the file contents into a directory of your choosing by right-clicking on the zip file and selecting Extract All . When you extract the contents of the .zip file, a directory named amq-clients-2.8.0-dotnet is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document.

Commands:
unzip amq-clients-2.8.0-dotnet-core.zip
<?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3"/> <add key="amq-clients" value=" <install-dir> /nupkg"/> </packageSources> </configuration>
Chapter 1. Introduction to Hammer Hammer is a powerful command-line tool provided with Red Hat Satellite 6. You can use Hammer to configure and manage a Satellite Server either through CLI commands or automation in shell scripts. Hammer also provides an interactive shell. 1.1. Hammer compared to Satellite web UI Compared to navigating the Satellite web UI, using Hammer can result in much faster interaction with the Satellite Server, as common shell features such as environment variables and aliases are at your disposal. You can also incorporate Hammer commands into reusable scripts for automating tasks of various complexity. Output from Hammer commands can be redirected to other tools, which allows for integration with your existing environment. You can issue Hammer commands directly on the base operating system running Red Hat Satellite. Access to base operating system on Satellite Server is required to issue Hammer commands, which can limit the number of potential users compared to the Satellite web UI. Although the parity between Hammer and the Satellite web UI is almost complete, the Satellite web UI has development priority and can be ahead especially for newly introduced features. 1.2. Hammer compared to Satellite API For many tasks, both Hammer and Satellite API are equally applicable. Hammer can be used as a human friendly interface to Satellite API, for example to test responses to API calls before applying them in a script (use the -d option to inspect API calls issued by Hammer, for example hammer -d organization list ). Changes in the API are automatically reflected in Hammer, while scripts using the API directly have to be updated manually. In the background, each Hammer command first establishes a binding to the API, then sends a request. This can have performance implications when executing a large number of Hammer commands in sequence. In contrast, a script communicating directly with the API establishes the binding only once. For more information, see the Using the Satellite REST API . 1.3. Getting help View the full list of hammer options and subcommands by executing: Use --help to inspect any subcommand, for example: You can search the help output using grep , or redirect it to a text viewer, for example:

Commands:
hammer --help
hammer organization --help
hammer | less
Chapter 17. Web Servers and Services Apache HTTP Server 2.4 Version 2.4 of the Apache HTTP Server ( httpd ) is included in Red Hat Enterprise Linux 7, and offers a range of new features: an enhanced version of the "Event" processing module, improving asynchronous request process and performance; native FastCGI support in the mod_proxy module; support for embedded scripting using the Lua language. More information about the features and changes in httpd 2.4 can be found at http://httpd.apache.org/docs/2.4/new_features_2_4.html . A guide to adapting configuration files is also available: http://httpd.apache.org/docs/2.4/upgrading.html . MariaDB 5.5 MariaDB is the default implementation of MySQL in Red Hat Enterprise Linux 7. MariaDB is a community-developed fork of the MySQL database project, and provides a replacement for MySQL. MariaDB preserves API and ABI compatibility with MySQL and adds several new features; for example, a non-blocking client API library, the Aria and XtraDB storage engines with enhanced performance, better server status variables, and enhanced replication. Detailed information about MariaDB can be found at https://mariadb.com/kb/en/what-is-mariadb-55/ . PostgreSQL 9.2 PostgreSQL is an advanced Object-Relational database management system (DBMS). The postgresql packages include the PostgreSQL server package, client programs, and libraries needed to access a PostgreSQL DBMS server. Red Hat Enterprise Linux 7 features version 9.2 of PostgreSQL. For a list of new features, bug fixes and possible incompatibilities against version 8.4 packaged in Red Hat Enterprise Linux 6, please refer to the upstream release notes: http://www.postgresql.org/docs/9.2/static/release-9-0.html http://www.postgresql.org/docs/9.2/static/release-9-1.html http://www.postgresql.org/docs/9.2/static/release-9-2.html Or the PostgreSQL wiki pages: http://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.0 http://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.1 http://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.2

Commands:
A.3. Enabling and Disabling the Feature To disable the consistent network device naming on Dell systems that would normally have it on by default, pass the following option on the boot command line, both during and after installation: To enable this feature on other system types that meet the minimum requirements (see Section A.2, "System Requirements" ), pass the following option on the boot command line, both during and after installation: Unless the system meets the minimum requirements, this option will be ignored and the system will boot with the traditional network interface name format. If the biosdevname install option is specified, it must remain as a boot option for the lifetime of the system.

Commands:
biosdevname=0
biosdevname=1
B.21.2. RHSA-2010:0966 - Critical: firefox security update Updated firefox packages that fix several security issues are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Mozilla Firefox is an open source web browser. CVE-2010-3766 , CVE-2010-3767 , CVE-2010-3772 , CVE-2010-3776 , CVE-2010-3777 Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox. CVE-2010-3771 A flaw was found in the way Firefox handled malformed JavaScript. A website with an object containing malicious JavaScript could cause Firefox to execute that JavaScript with the privileges of the user running Firefox. CVE-2010-3768 This update adds support for the Sanitiser for OpenType (OTS) library to Firefox. This library helps prevent potential exploits in malformed OpenType fonts by verifying the font file prior to use. CVE-2010-3775 A flaw was found in the way Firefox loaded Java LiveConnect scripts. Malicious web content could load a Java LiveConnect script in a way that would result in the plug-in object having elevated privileges, allowing it to execute Java code with the privileges of the user running Firefox. CVE-2010-3773 It was found that the fix for CVE-2010-0179 was incomplete when the Firebug add-on was used. If a user visited a website containing malicious JavaScript while the Firebug add-on was enabled, it could cause Firefox to execute arbitrary JavaScript with the privileges of the user running Firefox. CVE-2010-3774 A flaw was found in the way Firefox presented the location bar to users. A malicious website could trick a user into thinking they are visiting the site reported by the location bar, when the page is actually content controlled by an attacker. CVE-2010-3770 A cross-site scripting (XSS) flaw was found in the Firefox x-mac-arabic, x-mac-farsi, and x-mac-hebrew character encodings. Certain characters were converted to angle brackets when displayed. If server-side script filtering missed these cases, it could result in Firefox executing JavaScript code with the permissions of a different website. For technical details regarding these flaws, refer to the Mozilla security advisories for Firefox 3.6.13: http://www.mozilla.org/security/known-vulnerabilities/firefox36.html#firefox3.6.13 All Firefox users should upgrade to these updated packages, which contain Firefox version 3.6.13, which corrects these issues. After installing the update, Firefox must be restarted for the changes to take effect.

Commands:
Chapter 19. Tracking the last login time without setting a lockout policy You can use the Account Policy plug-in to track user login times without setting an expiration time or inactivity period. In this case, the plug-in adds the lastLoginTime attribute to user entries. 19.1. Configuring the Account Policy plug-in to record the last login time Follow this procedure to record the last login time of users in the lastLoginTime attribute of user entries. Procedure Enable the Account Policy plug-in: # dsconf -D " cn=Directory Manager " ldap://server.example.com plugin account-policy enable Create the plug-in configuration entry to record login times: # dsconf -D " cn=Directory Manager " ldap://server.example.com plugin account-policy config-entry set " cn=config,cn=Account Policy Plugin,cn=plugins,cn=config " --always-record-login yes --state-attr lastLoginTime This command uses the following options: --always-record-login yes : Enables logging of the log in time. --state-attr lastLoginTime : Configures that the Account Policy plug-in stores the last log in time in the lastLoginTime attribute of users. Restart the instance: # dsctl instance_name restart Verification Log in to Directory Server as a user. For example, run a search: # ldapsearch -H ldap://server.example.com -x -D " uid=example,ou=People,dc=example,dc=com " -W -b " dc=example,dc=com " Display the lastLoginTime attribute of the user you used in the step: # ldapsearch -H ldap://server.example.com -x -D " cn=Directory Manager " -W -b " uid=example,ou=people,dc=example,dc=com " lastLoginTime ... dn: uid=example,ou=People,dc=example,dc=com lastLoginTime: 20210913091435Z If the lastLoginTime attribute exists and Directory Server updated its value, recording of the last login time works.

Commands:
dsconf -D " cn=Directory Manager " ldap://server.example.com plugin account-policy enable
dsconf -D " cn=Directory Manager " ldap://server.example.com plugin account-policy config-entry set " cn=config,cn=Account Policy Plugin,cn=plugins,cn=config " --always-record-login yes --state-attr lastLoginTime
dsctl instance_name restart
ldapsearch -H ldap://server.example.com -x -D " uid=example,ou=People,dc=example,dc=com " -W -b " dc=example,dc=com "
ldapsearch -H ldap://server.example.com -x -D " cn=Directory Manager " -W -b " uid=example,ou=people,dc=example,dc=com " lastLoginTime dn: uid=example,ou=People,dc=example,dc=com lastLoginTime: 20210913091435Z
3.5. Storage Storage for virtual machines is abstracted from the physical storage used by the virtual machine. It is attached to the virtual machine using the paravirtualized or emulated block device drivers. 3.5.1. Storage Pools A storage pool is a file, directory, or storage device managed by libvirt for the purpose of providing storage to virtual machines. Storage pools are divided into storage volumes that store virtual machine images or are attached to virtual machines as additional storage. Multiple guests can share the same storage pool, allowing for better allocation of storage resources. Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information. Local storage pools Local storage pools are attached directly to the host server. They include local directories, directly attached disks, physical partitions, and Logical Volume Management (LVM) volume groups on local devices. Local storage pools are useful for development, testing and small deployments that do not require migration or large numbers of virtual machines. Local storage pools may not be suitable for many production environments, because they do not support live migration. Networked (shared) storage pools Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required when migrating virtual machines between hosts with virt-manager , but is optional when migrating with virsh . Networked storage pools are managed by libvirt .

Commands:
Chapter 11. Editing applications You can edit the configuration and the source code of the application you create using the Topology view. 11.1. Prerequisites You have created and deployed an application on OpenShift Dedicated using the Developer perspective . You have logged in to the web console and have switched to the Developer perspective. 11.2. Editing the source code of an application using the Developer perspective You can use the Topology view in the Developer perspective to edit the source code of your application. Procedure In the Topology view, click the Edit Source code icon, displayed at the bottom-right of the deployed application, to access your source code and modify it. Note This feature is available only when you create applications using the From Git , From Catalog , and the From Dockerfile options. 11.3. Editing the application configuration using the Developer perspective You can use the Topology view in the Developer perspective to edit the configuration of your application. Note Currently, only configurations of applications created by using the From Git , Container Image , From Catalog , or From Dockerfile options in the Add workflow of the Developer perspective can be edited. Configurations of applications created by using the CLI or the YAML option from the Add workflow cannot be edited. Prerequisites Ensure that you have created an application using the From Git , Container Image , From Catalog , or From Dockerfile options in the Add workflow. Procedure After you have created an application and it is displayed in the Topology view, right-click the application to see the edit options available. Figure 11.1. Edit application Click Edit application-name to see the Add workflow you used to create the application. The form is pre-populated with the values you had added while creating the application. Edit the necessary values for the application. Note You cannot edit the Name field in the General section, the CI/CD pipelines, or the Create a route to the application field in the Advanced Options section. Click Save to restart the build and deploy a new image. Figure 11.2. Edit and redeploy application

Commands: