@JaredBusch said in Linux: What is the EPEL:

@scottalanmiller said in Linux: What is the EPEL:

d "frozen" to make for the core RH

To make what?

Fixed

@black3dynamite Good call. I had to make some adjustments to SELinux.

@stacksofplates said in Open Firewall Ports on CentOS 7 and RHEL 7:

@coliver said in Open Firewall Ports on CentOS 7 and RHEL 7:

@stacksofplates said in Open Firewall Ports on CentOS 7 and RHEL 7:

@coliver said in Open Firewall Ports on CentOS 7 and RHEL 7:

@scottalanmiller said in Open Firewall Ports on CentOS 7 and RHEL 7:

@coliver said in Open Firewall Ports on CentOS 7 and RHEL 7:

Did anyone ever figure out if there was a way to setup files for firewalld? Or was the XML service files the way to go?

XML I think.

That's what I was afraid of. We're using IPTables on all of our OEL7 servers right now but I think moving to the default firewalld may be a good idea. I'll have to look into the XML config and see how much more difficult, if at all, it is over the IPTables file. It's a shame we can't just copy a single file around anymore but the XML files probably won't be too much more difficult.

Ya it's not bad at all. Here's the config from my Identity Management server. It's pretty similar to /etc/sysconfig/system-config-firewall on RHEL 6, just in zone specific XML files.

<zone> <short>Public</short> <description>For use in public areas. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.</description> <service name="http"/> <service name="https"/> <service name="ntp"/> <service name="dhcpv6-client"/> <service name="kerberos"/> <service name="ldaps"/> <service name="ssh"/> <service name="dns"/> <service name="ldap"/> </zone>

Those services are predefined right? You can also build your own services via the same process.

Ya and you can define specific ports. I prob could have grabbed a better example.

No, I think I've got it just need to investigate actually setting these up.

@jaredbusch said in ScreenConnect High CPU Usage:

@scottalanmiller said in ScreenConnect High CPU Usage:

Have another system doing this this week. Been about eight hours so far. We are thinking that it is just doing the database rebuild and compression work. But it is insane how much CPU gets used for this.

Do you not have it doing this on a regular schedule?

Not my system, it was moved to a different server and had to be rebuilt.

@scottalanmiller said in Installing Linux Malware Detect and ClamAV on CentOS 7:

@travisdh1 said in Installing Linux Malware Detect and ClamAV on CentOS 7:

Any reason to use LMD instead of or in addition to rkhunter?

Doesn't rkhunter focus only on root kits?

Mostly, but this was the first time I remember hearing about LMD.

@scottalanmiller Also, using just using the root domain name for the conf file name is potentially confusing depending on how much you are hosting.

Even for my gaming website, I have a bunch of sub domains setup.

www.daerma.com.conf goes to the root and www.
oc.daerma.com.conf is owncloud
obelisk.daerma.com.conf is my nodeBB forum

That does not even get into what do you do about the ones that you have multiple TLD names for such as .it, .com, .org, etc.

I can't believe that they don't have a RHEL package at least!

@scottalanmiller said in Installing a Basic LAMP Stack on CentOS 7:

@NashBrydges said in Installing a Basic LAMP Stack on CentOS 7:

@scottalanmiller I haven't yet. About to give it a try. Stuck to legacy since that was what I was reading everywhere.

Where is everywhere? Technet says to not use legacy.

https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/supported-centos-and-red-hat-enterprise-linux-virtual-machines-on-hyper-v

Legacy is a fallback driver that you never want to use, it's low performance and high overhead. If you needed that for CentOS, it would make Hyper-V a silly, non-production ready platform. But Hyper-V is a good, solid performer.

Not only that, but I install all of my CentOS 7 VM's as Generation 2 when on Hyper-V they work perfectly with default settings for everything except secure boot. Uncheck secure boot. Everything else is 100% default settings.

Great job @scottalanmiller and welcome aboard!

Hope you enjoyed the experience!

Now if you want to play with it, I recommend you to use our CLI (http://docs.openio.io/cli-reference) or you can deploy our S3/Swift implementation (https://github.com/open-io/oio-sds/wiki/Install-Guide---OpenIO-Swift-S3-gateway).

Feel free to send me some feedbacks, I'm here to help!

Guillaume.
Product Manager & Co-Founder @ OpenIO

@DustinB3403 said in Linux: Checking Filesystem Usage with df:

Will there be a topic on "managing inode in linux"

Yes, but it is going to go into an "Advanced Topics" section. Just as LVM and MD will have high level "normal" admin sections and eventually delve much deeper in advanced sections. I want to cover everything in a "normal admin" capacity like you would learn from the RHCE up front. Then go back and cover the nitty gritty details that other admin books don't. So it will basically take two passes but the hope is that the first pass will take you from "starting point" to "competent Linux Admin" then the second part will go where normal admin guides don't tread.

It doesn't update as "new" when I just update the list. Only if I comment on the thread.

Who knows, everyone is pretty confused by this one.

The "working data" that I mentioned that scrolls by quickly before our summary chart appears from this example looks like the below output. Generally we can ignore this, but it can be useful should there be an error to see where something has gone wrong.

$ yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.lga7.us.voxel.net * epel: mirror.cs.princeton.edu * extras: mirror.lug.udel.edu * updates: mirror.trouble-free.net Resolving Dependencies --> Running transaction check ---> Package NetworkManager.x86_64 1:1.0.0-16.git20150121.b4ea599c.el7_1 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-adsl.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-adsl.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-29.el7_2 will be an update --> Processing Dependency: libbluetooth.so.3()(64bit) for package: 1:NetworkManager-bluetooth-1.0.6-29.el7_2.x86_64 ---> Package NetworkManager-glib.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-glib.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-libnm.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-libnm.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-team.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-team.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-tui.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-tui.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wifi.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wifi.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wwan.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wwan.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package avahi.x86_64 0:0.6.31-14.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-libs.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-libs.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-license.noarch 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-license.noarch 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package ca-certificates.noarch 0:2015.2.4-71.el7 will be updated ---> Package ca-certificates.noarch 0:2015.2.6-70.1.el7_2 will be an update ---> Package coreutils.x86_64 0:8.22-12.el7_1.2 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7_2.1 will be an update ---> Package cronie.x86_64 0:1.4.11-13.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-19.2.el7 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-20.el7_2 will be an update ---> Package device-mapper.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package filebeat.x86_64 0:1.1.0-1 will be updated ---> Package filebeat.x86_64 0:1.2.1-1 will be an update ---> Package glibc.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package glibc-common.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc-common.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package htop.x86_64 0:1.0.3-3.el7 will be updated ---> Package htop.x86_64 0:2.0.1-1.el7 will be an update ---> Package initscripts.x86_64 0:9.49.24-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7_2.2 will be an update ---> Package kernel.x86_64 0:3.10.0-327.13.1.el7 will be installed ---> Package kernel-tools.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kexec-tools.x86_64 0:2.0.7-19.el7_1.2 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7_2.1 will be an update ---> Package kpartx.x86_64 0:0.4.9-85.el7 will be updated ---> Package kpartx.x86_64 0:0.4.9-85.el7_2.1 will be an update ---> Package krb5-libs.x86_64 0:1.13.2-10.el7 will be updated ---> Package krb5-libs.x86_64 0:1.13.2-12.el7_2 will be an update ---> Package libblkid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libblkid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libgudev1.x86_64 0:219-19.el7 will be updated ---> Package libgudev1.x86_64 0:219-19.el7_2.7 will be an update ---> Package libmount.x86_64 0:2.23.2-26.el7 will be updated ---> Package libmount.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libssh2.x86_64 0:1.4.3-10.el7 will be updated ---> Package libssh2.x86_64 0:1.4.3-10.el7_2.1 will be an update ---> Package libteam.x86_64 0:1.17-5.el7 will be updated ---> Package libteam.x86_64 0:1.17-6.el7_2 will be an update ---> Package libuuid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libuuid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package mariadb-libs.x86_64 1:5.5.44-2.el7.centos will be updated ---> Package mariadb-libs.x86_64 1:5.5.47-1.el7_2 will be an update ---> Package nss-util.x86_64 0:3.19.1-4.el7_1 will be updated ---> Package nss-util.x86_64 0:3.19.1-9.el7_2 will be an update ---> Package numactl-libs.x86_64 0:2.0.9-5.el7_1 will be updated ---> Package numactl-libs.x86_64 0:2.0.9-6.el7_2 will be an update ---> Package openldap.x86_64 0:2.4.40-8.el7 will be updated ---> Package openldap.x86_64 0:2.4.40-9.el7_2 will be an update ---> Package openssh.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-clients.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh-clients.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-server.x86_64 0:6.6.1p1-12.el7_1 will be updated ---> Package openssh-server.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package polkit.x86_64 0:0.112-5.el7 will be updated ---> Package polkit.x86_64 0:0.112-6.el7_2 will be an update ---> Package procps-ng.x86_64 0:3.3.10-3.el7 will be updated ---> Package procps-ng.x86_64 0:3.3.10-5.el7_2 will be an update ---> Package python-boto.noarch 0:2.38.0-2.el7 will be obsoleted ---> Package python-perf.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package python-perf.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package python-pyudev.noarch 0:0.15-7.el7 will be updated ---> Package python-pyudev.noarch 0:0.15-7.el7_2.1 will be an update ---> Package python2-boto.noarch 0:2.39.0-1.el7 will be obsoleting ---> Package screen.x86_64 0:4.1.0-0.19.20120314git3c2946.el7 will be updated ---> Package screen.x86_64 0:4.1.0-0.23.20120314git3c2946.el7_2 will be an update ---> Package selinux-policy.noarch 0:3.13.1-60.el7 will be updated ---> Package selinux-policy.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7_1.21 will be updated ---> Package selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package sudo.x86_64 0:1.8.6p7-16.el7 will be updated ---> Package sudo.x86_64 0:1.8.6p7-17.el7_2 will be an update ---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated ---> Package systemd.x86_64 0:219-19.el7 will be updated ---> Package systemd.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-libs.x86_64 0:219-19.el7 will be updated ---> Package systemd-libs.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-python.x86_64 0:219-19.el7 will be updated ---> Package systemd-python.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-sysv.x86_64 0:219-19.el7 will be updated ---> Package systemd-sysv.x86_64 0:219-19.el7_2.7 will be an update ---> Package teamd.x86_64 0:1.17-5.el7 will be updated ---> Package teamd.x86_64 0:1.17-6.el7_2 will be an update ---> Package topbeat.x86_64 0:1.1.0-1 will be updated ---> Package topbeat.x86_64 0:1.2.1-1 will be an update ---> Package tuned.noarch 0:2.4.1-1.el7 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.1 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.3 will be an update ---> Package tzdata.noarch 0:2015g-1.el7 will be updated ---> Package tzdata.noarch 0:2016c-1.el7 will be an update ---> Package util-linux.x86_64 0:2.23.2-26.el7 will be updated ---> Package util-linux.x86_64 0:2.23.2-26.el7_2.2 will be an update --> Running transaction check ---> Package bluez-libs.x86_64 0:5.23-4.el7 will be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-229.7.2.el7 will be erased ---> Package kernel.x86_64 0:3.10.0-229.11.1.el7 will be erased --> Finished Dependency Resolution Dependencies Resolved

That's a good question... when does chrooting make more sense than containers today?

Storage is one. Lots of people use chroot jails for storage purposes. Containers are heavier than chrooting which has effectively no impact on any resources.