similar to: /var/run/... being deleted :((

On Wed, 11 Oct 2017, Lamar Owen wrote: > If the maintainers of packages that want to run well on CentOS 7 need to have > /var/run/$some-file persistence (or pseudo-persistence, which is the current > behavior enabled by re-creating said files) then those maintainers will need > to change their packages to match actual behavior or file a bug report with > upstream to change the

On 10/13/2017 10:19 AM, Anand Buddhdev wrote: > .. > Stop trying to force a square peg into a round hole. Whee, I just _know_ I'm going to be positively skewered (and maybe even plonked!) for this.... but, hey, it's Friday, and this post is meant to be a bit funny.? So lighten up, and enjoy a short read. obHumor: I actually have a piece of furniture (a small table) with square

On 09/21/2017 08:14 AM, hw wrote: > what keeps deleting files and directories under /var/run?? Having them > deleted > is extremely annoying because after a reboot, things are suddenly > broken because > services don?t start. You've received a lot of advice, criticism, and information from this original post, and I'm not going to rehash any of those things.? If

While I empathize with your predicament, I generally prefer not to have expletives in my inbox. Also, what has this to do with markdown? On Jul 5, 2013 7:20 PM, "bowerbird" <bowerbird at aol.com> wrote: > fan_fucking_tastic. > > somebody hit another one of the dead skunks on this road. > > -bowerbird > > _______________________________________________ >

On 13/10/2017 16:02, Michael Hennebry wrote: Hi Michael, > I see at least two possible intermediate results: > The RHEL 7 folks do something, perhaps make a package, > to make pseudo-persistence super easy to get. > The RHEL 7 folks do something, perhaps make a package, > to allow users to fix this particular problem, e.g. > by adding pseudo-persisitence for a file used by a

This is pretty much a retorical question, although I would like to know the extent of the problem and how quickly it's gonna be sorted. My problem has already been described in a previous post, i.e. clamd fails after a reboot. The cause apparently is that /run and therefore /var/run has at some point been moved onto tmpfs which means that it doesn't survive a reboot. The effect of

Jonathan Billings <billings at negate.org> writes: > On Oct 3, 2017, at 13:12, hw <hw at adminart.net> wrote: >> >> I?m using the packages from mariadb.org. The old version that comes in >> Centos isn?t recommended, and I need features only the newer versions >> provide. >> >> >> Lighttpd is from epel, and it has basically the same

Commit a6330e9d3af0f5286f1d53d909fd868387b67f69 enabled /run for systemd-tmpfiles: while this works fine in most of the cases, there are few tmpfiles configurations that still references /var/run instead of /run. As result, include also /var/run in the systemd-tmpfiles execution. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init

hey folks, we are migrating our tomcat setup over to centos 7. Im converting init-scripts over to systemd services and whatnot.. One thing that Ive noticed is that my systemd startup script cant seem to write to /var/run as a non-root user to drop a pidfile.. If I create a directory in /var/run owned by my user, it gets wiped out on reboot. Ive searched and found this

Alexander Dalloz <ad+lists at uni-x.org> writes: > Am 01.10.2017 um 17:21 schrieb hw: >> Hi, >> >> how can I prevent files/directories like /var/run/mariadb from being >> deleted on reboot? Lighttpd has the same problem. >> >> This breaks services and makes servers non-restartable by anyone else >> but the administrator who needs to re-create

On Wednesday 04 October 2017 09:42:13 Anand Buddhdev wrote: > There's no need to do that (and it's also messy). Instead, if a package > needs a directory to exist in /var/run, then create your own config for > systemd-tmpfiles, and drop it into /etc/systemd/tmpfiles.d. Work with > CentOS 7, instead of fighting with it. > > Anand I saw reference to system-tmpfs in

On Fedora 20, every time the kernel updates, /var/run/asterisk owner is set to root.root. I'm running asterisk under user asterisk. Is there any way to keep /var/run/asterisk as asterisk.asterisk. Or do I find a new place to put asterisk.pid? sean

Hello List, with CentOS 7.2 it is not longer possible to run fail2ban on a Server ? I install a new CentOS 7.2 and the EPEL directory yum install fail2ban I don't change anything only I create a jail.local to enable the Filters [sshd] enabled = true .... ..... When I start afterward fail2ban systemctl status fail2ban is clean But systemctl status firewalld is broken ? firewalld.service -

Hi, how can I prevent files/directories like /var/run/mariadb from being deleted on reboot? Lighttpd has the same problem. This breaks services and makes servers non-restartable by anyone else but the administrator who needs to re-create the needed files and directories every time and has to figure out what selinux labels they need. This causes unnecessary downtimes. This is entirely

Mark Haney <mark.haney at neonova.net> writes: > On 10/03/2017 01:12 PM, hw wrote: >> >>> See >>> >>> https://developers.redhat.com/blog/2016/09/20/managing-temporary-files-with-systemd-tmpfiles-on-rhel7/ >>> >>> how to manage tmpfiles. >> Thanks, I?ll look into that. I wouldn?t consider a directory like >> /var/run/mariadb

Anand Buddhdev <anandb at ripe.net> writes: > On 05/10/2017 11:32, hw wrote: > >>> That directory isn't temporary. The files almost always are, but not >>> the directories. As I said, whatever it is you're doing, it's wrong. >>> I wouldn't continue to keep a setup like that as it's not standard >>> practice to keep data in

On Tuesday 03 October 2017 18:24:01 Mark Haney wrote: > What issue? That the PID is dropped on reboot?? What else are you > putting in there?? I'm beginning to question whether you know what > you're doing or not.? Lighttpd doesn't store any persistent info in > /var/run/ because, like everything else, /var/run isn't for persistent > data. Mark, Many Non-Centos

Been working on fail2ban, and trying to make it work with plain Jane install of Centos 7 Machine is a HP running 2 Quad core Xeons, 16 gig or ram and 1 plus TB of disk space. Very generic and vanilla. Current available epel repo version is fail2ban-0.9.1 Looking at the log file, fail2ban starts and stops fine, there isn't output though showing any login attempts being restricted.

P? Tue, 31 Dec 2019 18:53:38 +0000 John H Nyhuis <jnyhuis at uw.edu> skrev: > Just a random stab in the dark, but CEntOS6 was iptables, and CentOS7 > is firewalld. They take different fail2ban packages. > > CentOS6 = fail2ban > CentOS7 = fail2ban-firewalld > > Are you sure you are running the correct fail2ban package for your > firewall? (I screwed this up myself

On 10/04/2017 04:54 AM, Mark Haney wrote: > Why is it so hard for people to understand that var/run IS NOT > PERSISTENT and was never meant to be?? Do they not teach basic Unix > concepts anymore? http://www.pathname.com/fhs/pub/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA While FHS notes that *files* should be cleared during the boot process, it does not indicate that directories should