similar to: how to prevent files and directories from being deleted?

You can try chattr? https://en.wikipedia.org/wiki/Chattr 2017-10-01 12:26 GMT-03:00 Alexander Dalloz <ad+lists at uni-x.org>: > 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

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 > directories every time and has to figure out what selinux

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

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 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 > directories every time and has to figure out what selinux labels they

We have a bunch of lists hosted on a CentOS-4.9 server running sendmail and mailman that we are moving to a CentOS-6 vm running postfix and mailman. I am testing the setup and I am running into a problem no doubt caused by my own ignorance wrt postfix. Based on groking the web I discovered that the recommended way to configure postfix to work with mailman is a script called

On Mon, November 16, 2015 16:39, Nick Bright wrote: > On 11/6/2015 3:58 PM, James Hogarth wrote: >> I have a couple of relevant articles you may be interested in ... >> >> On assigning the zone via NM: >> https://www.hogarthuk.com/?q=node/8 >> >> Look down to the "Specifying a particular firewall zone" bit ... >> remember that if you edit the

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 way it is for > CentOS. And fun fact: not only RHEL 7 and thus CentOS

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 the mariadb packages provided for Centos by > the mariadb people. > > Perhaps

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 points to /run on CentOS7, so even if > > you think this disagrees with

On Tue, December 9, 2014 18:45, Alexander Dalloz wrote: > Am 09.12.2014 um 23:04 schrieb James B. Byrne: >> Applied policy update. Now I see these occasionally. But by the time I try >> and >> see what the matter is the file is gone: > > Why do you start a new thread instead of continuing the old one about > the very same topic? > If you have a way to thread

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

I am investigating using rpm to package one of our in house applications. This software started life as a sub-system within a Ruby-on-Rails application but has now been extracted into its own standalone package, none of which has any httpd access. The local package under consideration will run as a set of cron jobs under a designated userid. There will be no user interaction. A remote database

I changed the entries in smb4.conf (smb.conf) to this: [global] . . . dns update command = /usr/local/sbin/samba_dnsupdate nsupdate command = /usr/local/bin/samba-nsupdate -d -g And this is what results when I run: samba_dnsupdate --verbose -d8 --all-names . . . update(nsupdate): SRV _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.brockley.harte-lyne.ca

I am testing DC administration using samba-4.10.15 on FreeBSD-12.1p6 and have run across this: [root at smb4-2 ~ (master)]# samba-tool domain join BROCKLEY.HARTE-LYNE.CA DC -U"BROCKLEY\administrator" INFO 2020-06-25 14:26:10,692 pid:47306 /usr/local/lib/python3.7/site-packages/samba/join.py #104: Finding a writeable DC for domain 'BROCKLEY.HARTE-LYNE.CA' INFO 2020-06-25

This is all the diagnostic information I can think of at the moment: [root at smb4-1 ~ (master)]# klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: administrator at BROCKLEY.HARTE-LYNE.CA Issued Expires Principal Jul 2 10:35:11 2020 Jul 2 20:35:11 2020 krbtgt/BROCKLEY.HARTE-LYNE.CA at BROCKLEY.HARTE-LYNE.CA [root at smb4-1 ~ (master)]# grep nsup

> Could be because you added the wrong line to your smb4.conf (why does > freebsd call it smb4.conf ?), Why does freebsd put these things in /usr/local/etc/? Some questions have answers that are not worth the effort to know. > try: > nsupdate command = /usr/local/sbin/nsupdate -g I did catch that error earlier. But it makes no difference. samba_dnsupdate does not give any

Thank you for your patience. On Tue, June 30, 2020 16:48, Rowland penny wrote: > > From 'man smb.conf': > > nsupdate command (G) > > This option sets the path to the nsupdate command which is used for > GSS-TSIG dynamic DNS updates. > > Default: nsupdate command = /usr/bin/nsupdate -g > > dns update command (G) > > This

I have introduced some error in my dns resolution and I would like some help fixing it as I cannot seem to detect what I have done wrong. Briefly the setup is this: name servers: DNS01 - 216.185.71.33 DNS02 - 209.47.176.33 DNS03 - 216.185.71.34 DNS04 - 209.47.176.34 - offline DNS01 is a master DNS02-04 are slaves of 216.185.71.33 All are listed as authoritative for the zone test.com The