There doesn't appear to be a way to obtain the account creation date using the API (which is what the ipa CLI tool uses), but it is available directly via LDAP as an operational attribute called createTimestamp.
ldapsearch -b 'cn=users,cn=accounts,dc=SUB,dc=DOM' [options] "uid=$user" createTimestamp
You should remove the old corrupted RPM database and rebuild the RPM database. You can do these by running:
rm -f /var/lib/rpm/__db*
Note that the usual cause of this problem is interrupting a package installation, update or removal. You should ensure that such actions are not interrupted by the user, and that your system has proper backup ...
Most major patch update, since there is many libraries that need to account for the kernel. So basically, look for the kernel, which usually happens around the second or 3rd week of the month. If you have a management system like Foreman/Katello, you will know when there is large sync.
You can download package and it's all dependencies with yum install. For example to download all required rpms into packages directory:
yum install --downloadonly --downloaddir=packages mysql++-devel
After all dependencies has been downloaded, you can copy the packages to the target host and install them with
yum install *
CentOS and RHEL are actually different, despite one being "clone" of the other.
The canonical name for the repository in question is actually CodeReady Linux Builder.
However, it is trademarked, and as such, in CentOS it has a different name - PowerTools.
Since you are using RHEL, you should enable CodeReady Linux Builder repository:
I was able to get it to work by creating an override file for the mariadb systemd service and adding
ExecStart=/usr/bin/mysqld_safe --defaults-file=/nfspath/%H_my.cnf --basedir=/usr
Just to clarify, the --defaults-file option has to be the first argument in the line, it would not work otherwise. Thank you again for both of your inputs!
I don't have a RHEL system handy, but assuming it is pretty close to centos7.
Sure seems like you could easily handle this by overriding mariadb.service unit somehow.
Perhaps add a ExecStartPre that adds a script that will replace the my.cnf with a symlink of /etc/my.cnf to something like /nfspath/$(hostname -f)_my.cnf.
Or perhaps there is a way to just ...
Yes, it will create an issue.
The file will continue to exist on disk as long as any process has it open. When you delete it, the directory entry pointing to the file is deleted and its reference count is reduced. But since some process already had the file open, the reference count is 2, not 1, and is decremented to 1, not 0.
After the process writing to ...
The answer is that Openscap cannot perform remote remediations. oscap-chroot and oscap-ssh are meant for scans only. The recommended solution, from what I can tell, is to use oscap xccdf generate fix using the results.xml file generated by oscap-chroot. Then run this remediation script manually against the remote host.
If your log records have keys, you can use ausearch -k <keyname> to get all events with that key associated.
If you combine it with --checkpoint you can read the log incrementally. However, you will need separate checkpoint-files for every key you're filtering for, of course.
In addition to the rule that allows passwordless sudo for specific commands, you also need some other sudo rule which allows your user to run ALL commands with sudo.
The default sudo config allows users in the wheel group to run ALL commands with sudo (after supplying a password) and users who should have such access should be placed in this group.
# usermod ...
You can log in to your Red Hat account and download the SRPM (source code RPM) package for any package for which you have a valid subscription. These contain the original source code for the software and all of the patches Red Hat applied to it.
Click on Downloads, then choose the product you want to obtain source code for, then click Packages to download ...
All RPM packages are built from SRPM , source code packages which you can download.
Those SRPM packages typically contain among others a pristine source code release downloaded from an upstream open source project as well as all (code) changes / additions made by the package maintainer (Red Hat).
The official RHEL images in Amazon AWS are provided and maintained by Red Hat themselves.
Red Hat runs its own update infrastructure within every AWS region so that you can get official updates.
From the Frequently Asked Questions about RHEL on AWS:
Red Hat Enterprise Linux on Amazon EC2 is maintained by Red Hat and is identical to the version of Red Hat ...
You can look for events with a type of USER_LOGIN and USER_LOGOUT in /var/log/audit/audit.log for remote logins, e.g. with ssh.
Use of sudo and other user/role changes will be logged with a type of USER_START and LOGIN, and USER_END. See also USER_AUTH for authentication attempts.
The type of LOGIN also records local GUI console logins, but as far as I can ...