On 09/10/2017 13:54, hw wrote:
Mark,
> It is quite obvious that Centos causes issues because it is not
> following the FHS.
Stop right there. CentOS *is* following the FHS. Can you please stop
this whiny complaint against CentOS, and just accept that the packages
you're using are not properly
On 09/10/2017 12:38, hw wrote:
>> 4. Finally, if you as a sysadmin are using a package from a repo that
>> isn't CentOS or EPEL, and this package is not following the CentOS
>> packaging protocol for data in /run, then it is YOUR own responsibility
>> to fix the package, or create your own
On Mon, October 9, 2017 3:31 pm, Jon LaBadie wrote:
> On Mon, Oct 09, 2017 at 08:32:32PM +0200, Alexander Dalloz wrote:
>> Am 09.10.2017 um 17:54 schrieb Jonathan Billings:
>> > I think that the important learning points today are:
>> >
>> > 1.) CentOS7 (and any other distro that uses systemd)
On Mon, Oct 09, 2017 at 08:32:32PM +0200, Alexander Dalloz wrote:
> Am 09.10.2017 um 17:54 schrieb Jonathan Billings:
> > I think that the important learning points today are:
> >
> > 1.) CentOS7 (and any other distro that uses systemd) will have /run as
> > a tmpfs filesystem, and /var/run
>
> Best practises also involve to generally not delete files unless you can
> be sure that they can be deleted. That is probably what the FHS
> intended by specifying that files in /var/run must be deleted/truncated
> at boot time, assuming that the programs that created them would do this
>
Am 09.10.2017 um 17:54 schrieb Jonathan Billings:
I think that the important learning points today are:
1.) CentOS7 (and any other distro that uses systemd) will have /run as
a tmpfs filesystem, and /var/run points to /run on CentOS7, so even if
you think this disagrees with the FHS, that's the
On Mon, Oct 09, 2017 at 12:38:41PM +0200, hw wrote:
> I´m not whining, and it´s not my fault that someone came up with the
> extremely stupid idea to use a ramdisk for /var/run. It´s also not my
> fault that lighttpd appears not to be packaged the way it would need to
> be, and the same goes for
On Mon, Oct 09, 2017 at 02:06:35PM +0200, hw wrote:
> > If the EPEL package did too, then there could be serious problems with
> > that package. However, I see that it has a
> > /usr/lib/tmpfiles.d/lighttpd.conf, so it is ok.
>
> Hm, then how come it´s so troublesome?
>
> I have
Mark Haney writes:
> On 10/04/2017 08:46 AM, Gary Stainburn wrote:
>> On Wednesday 04 October 2017 13:39:30 Mark Haney wrote:
>>> I'll end this by saying, I hope the production servers you have don't
>>> provide critical services that could jeopardize the lives of people.
Gary Stainburn writes:
> 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
Gordon Messmer writes:
> 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?
>
>
>
Mark Haney writes:
> On 10/04/2017 04:23 AM, Gary Stainburn wrote:
>>
>> Mark, Many Non-Centos originated packages create directories in /var/run as
>> part of the install, and expect them to still exist after a reboot.
>>
>> They then fail when starting the service
Mark Haney writes:
> It's quite obvious you aren't using Centos packages.
Again: lighttpd is from epel.
See [1]: "EPEL packages are usually based on their Fedora counterparts
and will never conflict with or replace packages in the base Enterprise
Linux distributions."
Jonathan Billings writes:
> On Oct 3, 2017, at 13:12, hw 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
Anand Buddhdev 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
Mark Haney writes:
> On 10/04/2017 08:22 AM, Gary Stainburn wrote:
>> On Wednesday 04 October 2017 12:54:44 Mark Haney wrote:
>>> Sorry, but if you have to use packages that don't originate from CentOS
>>> and they do that, then I wouldn't use them. Period. I'd compile
Harold Toms writes:
> On 01/10/17 16:21, hw wrote:
>> 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
It's quite obvious you aren't using Centos packages. If you refuse to do
as best practices insist (and have for nearly HALF A CENTURY) then no one
here can help you. It seems to me that 1) you'd be better off compiling
from source for your environment, or 2) that you need to follow practices
Amand
*Thank you for the explanation .*
2017-10-05 7:00 GMT-03:00 Anand Buddhdev :
> 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
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 /var/run that isn't
Mark Haney 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
On 4 October 2017 at 16:06, wrote:
>I have not followed this thread since the first few emails... but has
> anyone suggested the SCL repo? I see mysql 5.6 and 5.7 there.
>
+1 for SCL -
https://www.softwarecollections.org/en/scls/rhscl/rh-mariadb101/
On 01/10/17 16:21, hw wrote:
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
On Wed, October 4, 2017 9:38 am, Gordon Messmer wrote:
> 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?
Well, Linux is not UNIX. And it never
On Tue, October 3, 2017 13:12, hw wrote:
> Alexander Dalloz 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
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*
On 10/04/2017 01:23 AM, Gary Stainburn wrote:
There is a solution that saves /var/run to disk at shutdown and restores it at
bootup but I can't remember what it is.
The simplest solution that comes to mind at 7:30am is simply bind
mounting a directory that's persistent. You'll still need to
Ok, folks,
I have not followed this thread since the first few emails... but has
anyone suggested the SCL repo? I see mysql 5.6 and 5.7 there.
mark "this is not the flamewar I'm looking for. I'll move along"
___
CentOS mailing list
On 10/04/2017 08:46 AM, Gary Stainburn wrote:
On Wednesday 04 October 2017 13:39:30 Mark Haney wrote:
I'll end this by saying, I hope the production servers you have don't
provide critical services that could jeopardize the lives of people.
I'd ask who you work for, to make sure I avoid them at
On 10/04/2017 08:39 AM, Mark Haney wrote:
> On 10/04/2017 08:22 AM, Gary Stainburn wrote:
>> On Wednesday 04 October 2017 12:54:44 Mark Haney wrote:
>>> Sorry, but if you have to use packages that don't originate from CentOS
>>> and they do that, then I wouldn't use them. Period. I'd compile from
On Wednesday 04 October 2017 13:39:30 Mark Haney wrote:
> I'll end this by saying, I hope the production servers you have don't
> provide critical services that could jeopardize the lives of people.
> I'd ask who you work for, to make sure I avoid them at all costs, but
> I'm not sure I'd be
On 10/04/2017 08:22 AM, Gary Stainburn wrote:
On Wednesday 04 October 2017 12:54:44 Mark Haney wrote:
Sorry, but if you have to use packages that don't originate from CentOS
and they do that, then I wouldn't use them. Period. I'd compile from
source before I used something configured that way.
On Wednesday 04 October 2017 12:54:44 Mark Haney wrote:
> Sorry, but if you have to use packages that don't originate from CentOS
> and they do that, then I wouldn't use them. Period. I'd compile from
> source before I used something configured that way.
This perspective to some extent employs
On 10/04/2017 04:23 AM, Gary Stainburn wrote:
Mark, Many Non-Centos originated packages create directories in /var/run as
part of the install, and expect them to still exist after a reboot.
They then fail when starting the service because they're trying to create a
PID / Lock file in a
On 04/10/2017 10:58, Gary Stainburn wrote:
> On Wednesday 04 October 2017 09:53:59 Gary Stainburn wrote:
>> I saw reference to system-tmpfs in Paul's post so I had a quick look. YUM
>> doesn't seem to know about it, but I'm sure Google will help.
>
> Sorry, meant systemd-tmpfiles
On a CentOS 7
On Wednesday 04 October 2017 09:53:59 Gary Stainburn wrote:
> I saw reference to system-tmpfs in Paul's post so I had a quick look. YUM
> doesn't seem to know about it, but I'm sure Google will help.
Sorry, meant systemd-tmpfiles
___
CentOS mailing list
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,
On 04/10/2017 10:23, Gary Stainburn wrote:
Hi Gary,
> Mark, Many Non-Centos originated packages create directories in /var/run as
> part of the install, and expect them to still exist after a reboot.
Those packages have been built poorly.
> They then fail when starting the service because
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
On Oct 3, 2017, at 13:12, hw 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 issue.
If the
On Tue, 3 Oct 2017, hw wrote:
Alexander Dalloz 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
On 10/03/2017 12:04 PM, hw wrote:
> marcos valentine writes:
>
>> You can try chattr?
>>
>> https://en.wikipedia.org/wiki/Chattr
>
> Wow, I never needed/used that. Being able to make files undeletable
> might be a very useful thing ...
>
>
as others have mentioned,
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 in any way as only temporary --- and
ect: Re: [CentOS] how to prevent files and directories from being deleted?
marcos valentine <msr.mail...@gmail.com> writes:
> You can try chattr?
>
> https://en.wikipedia.org/wiki/Chattr
Wow, I never needed/used that. Being able to make files undeletable
might be a very u
marcos valentine writes:
> You can try chattr?
>
> https://en.wikipedia.org/wiki/Chattr
Wow, I never needed/used that. Being able to make files undeletable
might be a very useful thing ...
--
"Didn't work" is an error.
___
Alexander Dalloz 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
>>
On 10/01/2017 11:21 AM, hw wrote:
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
On Mon, 2 Oct 2017, marcos valentine wrote:
You can try chattr?
https://en.wikipedia.org/wiki/Chattr
I think you'll find that'd do little useful on a tmpfs volume to preserve
files across reboots.
jh
___
CentOS mailing list
CentOS@centos.org
You can try chattr?
https://en.wikipedia.org/wiki/Chattr
2017-10-01 12:26 GMT-03:00 Alexander Dalloz :
> 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
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 the needed files and
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
51 matches
Mail list logo