@scottalanmiller I am on 6.4.something and it works for me on Fedora.

No Korora instance to test on

Strictly SYSCTL speaking, here's what I got so far:

kernel.randomize_va_space: sysctl.present: - value: 2 fs.protected_hardlinks: sysctl.present: - value: 1 fs.protected_symlinks: sysctl.present: - value: 1 net.ipv4.icmp_echo_ignore_broadcasts: sysctl.present: - value: 1 net.ipv4.icmp_ignore_bogus_error_responses: sysctl.present: - value: 1 net.ipv4.tcp_syncookies: sysctl.present: - value: 1 net.ipv4.conf.all.log_martians: sysctl.present: - value: 1 net.ipv4.conf.default.log_martians: sysctl.present: - value: 1 net.ipv4.conf.all.accept_source_route: sysctl.present: - value: 0 net.ipv4.conf.default.accept_source_route: sysctl.present: - value: 0 net.ipv4.conf.all.rp_filter: sysctl.present: - value: 1 net.ipv4.conf.default.rp_filter: sysctl.present: - value: 1 net.ipv4.conf.all.accept_redirects: sysctl.present: - value: 0 net.ipv4.conf.default.accept_redirects: sysctl.present: - value: 0 net.ipv4.conf.all.secure_redirects: sysctl.present: - value: 0 net.ipv4.conf.default.secure_redirects: sysctl.present: - value: 0 net.ipv4.ip_forward: sysctl.present: - value: 0 net.ipv4.conf.all.send_redirects: sysctl.present: - value: 0 net.ipv4.conf.default.send_redirects: sysctl.present: - value: 0 net.ipv4.conf.all.forwarding: sysctl.present: - value: 0 net.ipv6.conf.all.forwarding: sysctl.present: - value: 0 net.ipv4.conf.all.mc_forwarding: sysctl.present: - value: 0 net.ipv6.conf.all.mc_forwarding: sysctl.present: - value: 0 net.ipv6.conf.all.accept_source_route: sysctl.present: - value: 0 net.ipv6.conf.default.accept_source_route: sysctl.present: - value: 0 net.ipv6.conf.all.accept_redirects: sysctl.present: - value: 0 net.ipv6.conf.default.accept_redirects: sysctl.present: - value: 0

I know some of it may be redundant, as in they already may be set as such by default. My thinking is that should they become changed somehow, this will set it straight again.

Is this a bad way of thinking or simply not needed?

Are there any others a good idea or generally a best practice to include?

@jaredbusch said in SaltStack State: DNF-Automatic:

@tim_g said in SaltStack State: DNF-Automatic:

@jaredbusch said in SaltStack State: DNF-Automatic:

This would be the default one that comes down with the package. So that means there is nothing to grab.

Correct. I installed it on something first to get the config files, so I know what I'm working with.

That is more work and does nothing to help you when the file is updated upstream.

I did find how to easily modify files with SaltStack: https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.file.html#salt.modules.file.replace

But I think I would still rather host my own config file(s) at least for now. If they change in future updates, I'll just modify the config files on GitLab.

Anyways, link above for future reference when I come back to this later.

@black3dynamite said in Updating Fedora 26 to Fedora 27 with DNF:

@JaredBusch said in Updating Fedora 26 to Fedora 27 with DNF:

@black3dynamite said in Updating Fedora 26 to Fedora 27 with DNF:

@NerdyDad said in Updating Fedora 26 to Fedora 27 with DNF:

How often to you upgrade versus fresh install? Fresh install every other release? Any kind of best practice on this?

You can avoid compatibility with packages by using more flatpak apps instead.

Flatpak is not ready for prime time.

Why not?

And that's funny that you said prime time.

There's a post from Flatpak with prime time in the title.

Flatpak 1.0 Released, Ready for Prime Time
https://www.flatpak.org/press/2018-08-20-flatpak-1.0/

And @scottalanmiller coukd say sodiumsuite is awesome and ready for the masses. Still doesn’t make it true.

@JaredBusch said in Using dnf-automatic to keep Fedora up to date:

@FATeknollogee said in Using dnf-automatic to keep Fedora up to date:

There really need to be a setting for this in the Workstation GUI.

By default Fedora Workstation + Cinnamon uses dnfdragora which is a totally separate process.

Yes, I realize that.
This setting exists in Cockpit, no reason why it can't be in WS!

@scottalanmiller said in Installing WordPress on Fedora 25 and 26 Minimal install:

For ease and speed and better management, I highly recommend using WP-CLI for all of your downloading, updating, configuration, etc. One like of WP-CLI will eliminate most of this installation, while making it easier to maintain in the long run.

https://mangolassi.it/topic/13062/install-a-basic-wordpress-site-with-wp-cli

Yup, that's what I use now, I won't every go back!

https://mangolassi.it/topic/16084/installing-fedora-27-lamp-stack-plus-wordpress

@fateknollogee said in Fedora 26 Cinnamon KVM QEMU VM Guest dual-monitor:

Why not triple monitors at 2560 x 1600...

No need. I only have two 1080p monitors set up. So one at full screen and the other at 1600x900 works perfectly for my needs.

@scottalanmiller said in Fedora 26 Failing Salt Update:

@tim_g said in Fedora 26 Failing Salt Update:

Will that uninstall yum-utils? Isn't that still needed for a lot of things?

dnf-utils replaces it.

https://bugzilla.redhat.com/show_bug.cgi?id=1478593

@JaredBusch said in Install Telegram Desktop on Fedora 26 and newer with Cinnamon Desktop:

sudo dnf install telegram

It's now telegram-desktop

@tim_g
Do you know what tools and scripts that is available when installing hyperv-tools?

@mattbagan

Fedora
kimchi-2.5.0-0.fc25.noarch.rpm
wok-2.5.0-0.fc25.noarch.rpm

@ramblingbiped said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@stacksofplates said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@scottalanmiller said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@travisdh1 said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@jaredbusch said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@wirestyle22 said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@jaredbusch said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@travisdh1 said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@scottalanmiller said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@wirestyle22 said in Fedora 26 No Space Left on Device with Plenty of Space Available:

@scottalanmiller I could've sworn there was a post here related to a reboot solving it

Someone mentioned rebooting to try to solve it. But it did not (had already done that.) It was real files causing the issue, nothing orphaned. Literally, we were making 30K files an hour or so.

Tiny files to, right?

That is not relevant except for that fact that large files would have filled drive space and likely been noticed.

How is that not relevant? more files = more inodes being used

Size of the files is not relevant.

It actually makes sense that @scottalanmiller said it was mostly directories. Files of any size will almost always run out of drive space before inodes run out in 99.9999% of situations. This is the first time I've actually heard of this happening, ever.

Only not relevant for those who actually know about inodes already. The only reason I even know about them is they got mentioned in SGI's IRIX Sysadmin courses.

The one major exception is marker files. "touch thishappened" as a file automatically and never clean up and you are using inodes without using any space. That's who you can easily learn about inode depletion. But who does that?

People writing bad scripts that use lock files and forget to remove them.

That wouldn't create enough to do this though.

If you start using configuration management tools to manage infrastructure with code you get the chance to see some of these one-off oddities in the wild a little more frequently than you'd expect. Like having Java developers not use Java's log facilities to manage log rotation, and then having a generic log rotation configuration completely bork things by delete application logs that are still being accessed by the Java application.

I got to see this issue a few dozen times a few months ago before another of our Engineers disassociated the Java applications from our generic log rotation recipe.

Rebooting was the quick fix for us prior to fixing the actual problem.

Oh wow. Everything I have is managed with Ansible ( I can't even log in to servers), however all of the devs use Oracle APEX on separate systems so they don't really touch anything on my stuff. I'm sure I'd have it much worse if I had to manage their stuff.

@scottalanmiller said in Wanting to Dual boot to test KVM.. Where do i begin?:

Has this project been supplanted by the Fedora on the old desktop project?

Yes sir

@jaredbusch said in NextCloud: import users, groups and assignment:

In the time you have spent digging, you could have created all 20 users.

Go here: http://passwordsgenerator.net/plus/ Generate passwords 0_1501532564772_1d7d06c7-4b01-4476-b190-7b45a37f7546-image.png Set your default settings in Nextcloud (gear on bottom left) 0_1501532689678_87562b09-d58f-4993-9655-190aee22bd83-image.png Create users entering email addresses and selecting groups as you go. 0_1501532767284_dd2f6c53-e4ea-4d77-93a9-1047910201bf-image.png

Yea,.. I did that...Thanks though.

Open a crontab for the apache user

crontab -u apache -e */15 * * * * php -f /var/www/html/nextcloud/cron.php

@travisdh1 said in Updating Fedora 25 to Fedora 26 with DNF:

Fedora 27 Server note: The server edition hasn't been released yet according to https://getfedora.org/en/server/download/.

Using @scottalanmiller's upgrade instructions, it happily goes to 27.

That has nothing to do with DNF upgrades.

@zachary715 said in Certbot Apache plugin broken in Fedora 26:

@scottalanmiller said in Certbot Apache plugin broken in Fedora 26:

I ran into this issue, forgot about this thread, went through LetsEncrypt's threads and their solution for this problem led me... here! Very nice.

Just did the exact same thing. Let'sEncrypt forum had the link which led me here right about the time @JaredBusch was responding in my other thread.

It has been posted on here more than one time. I should probably find one of those posts and make @scottalanmiller tag it appropriately.

Edit: Or too slow..

@jmoore said in log.io on Fedora 26 Cannot Fine logging:

Oh ok, that sure is weird.

Just a bit.

@jmoore said in Trying to Install log.io on Fedora 26:

I finally got Log.io running and I like it. It will be really useful on the server for my website.

Nice, welcome to the club 🙂

My vote on this topic is Fedora. Just so few problems that i don't cause myself. Its made for Gnome.