Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #19208 > unrolled thread
| Started by | Custom Log <custom@log.abc> |
|---|---|
| First post | 2022-12-23 11:29 +0100 |
| Last post | 2022-12-24 08:37 +0100 |
| Articles | 6 — 3 participants |
Back to article view | Back to comp.lang.php
Additional .ini file Custom Log <custom@log.abc> - 2022-12-23 11:29 +0100
Re: Additional .ini file Arno Welzel <usenet@arnowelzel.de> - 2022-12-23 12:02 +0100
Re: Additional .ini file Custom Log <custom@log.abc> - 2022-12-23 13:33 +0100
Re: Additional .ini file Arno Welzel <usenet@arnowelzel.de> - 2022-12-23 16:16 +0100
Re: Additional .ini file "J.O. Aho" <user@example.net> - 2022-12-24 00:19 +0100
Re: Additional .ini file Custom Log <custom@log.abc> - 2022-12-24 08:37 +0100
| From | Custom Log <custom@log.abc> |
|---|---|
| Date | 2022-12-23 11:29 +0100 |
| Subject | Additional .ini file |
| Message-ID | <to3vu8$ii6$1@gioia.aioe.org> |
First of all $ php -i | grep --after-context=5 'Additional .ini' Additional .ini files parsed => /etc/php/8.1/cli/conf.d/10-opcache.ini, /etc/php/8.1/cli/conf.d/10-pdo.ini, /etc/php/8.1/cli/conf.d/15-xml.ini, /etc/php/8.1/cli/conf.d/20-calendar.ini, /etc/php/8.1/cli/conf.d/20-ctype.ini, /etc/php/8.1/cli/conf.d/20-dom.ini, OK!!! Now to the /etc/php/8.1/cli/conf.d directory I would like to add a personalized file of mine (custom-php.ini). $ touch /etc/php/8.1/cli/conf.d/custom-php.ini OK!!! But I wonder if it is a correct practice, given that /etc is a system directory (which contains system configuration files), and the system directories should not be touched. Would it therefore be advisable to specify (through the chef_ini_scan_dir) environment variable) an alternative directory?
[toc] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2022-12-23 12:02 +0100 |
| Message-ID | <k0lg6pFh9slU8@mid.individual.net> |
| In reply to | #19208 |
Custom Log, 2022-12-23 11:29: [...] > But I wonder if it is a correct practice, given that /etc is a system > directory (which contains system configuration files), and the system > directories should not be touched. No, there is no rule that system directories should not be touched. Of course you can adjust the configuration in /etc as needed. Only user processes should not change system files, so for example PHP scripts serving a website must not be allowed to modify files inside /etc - but of course you as administrator can adjust the files as needed. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Custom Log <custom@log.abc> |
|---|---|
| Date | 2022-12-23 13:33 +0100 |
| Message-ID | <to476r$1pke$2@gioia.aioe.org> |
| In reply to | #19209 |
Il 23/12/22 12:02, Arno Welzel ha scritto: > Custom Log, 2022-12-23 11:29: > > [...] >> But I wonder if it is a correct practice, given that /etc is a system >> directory (which contains system configuration files), and the system >> directories should not be touched. > > No, there is no rule that system directories should not be touched. Of > course you can adjust the configuration in /etc as needed. > > Only user processes should not change system files, so for example PHP > scripts serving a website must not be allowed to modify files inside > /etc - but of course you as administrator can adjust the files as needed. > However, a possible update (of the system) could lead to the overwriting of some of these files
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2022-12-23 16:16 +0100 |
| Message-ID | <k0lv1tFjt7bU1@mid.individual.net> |
| In reply to | #19210 |
Custom Log, 2022-12-23 13:33: > Il 23/12/22 12:02, Arno Welzel ha scritto: >> Custom Log, 2022-12-23 11:29: >> >> [...] >>> But I wonder if it is a correct practice, given that /etc is a system >>> directory (which contains system configuration files), and the system >>> directories should not be touched. >> >> No, there is no rule that system directories should not be touched. Of >> course you can adjust the configuration in /etc as needed. >> >> Only user processes should not change system files, so for example PHP >> scripts serving a website must not be allowed to modify files inside >> /etc - but of course you as administrator can adjust the files as needed. >> > > However, a possible update (of the system) could lead to the overwriting > of some of these files No, usually not, since apt and rpm both ask first before overwriting files. Usually you are notified about changes and can then decide wether to use the new version, keep the local version or merge the changes from the distribution to your local version. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | "J.O. Aho" <user@example.net> |
|---|---|
| Date | 2022-12-24 00:19 +0100 |
| Message-ID | <k0mrblFkm8mU1@mid.individual.net> |
| In reply to | #19208 |
On 23/12/2022 11.29, Custom Log wrote: > But I wonder if it is a correct practice, given that /etc is a system > directory (which contains system configuration files), and the system > directories should not be touched. It's just bogus, this are configuration files which the administrator of the system should tweak so that the machine is doing what the administrator needs it to be able to do. Just avoid making things writeable by everyone or files with passwords or private keys readable by anyone. > Would it therefore be advisable to specify (through the > chef_ini_scan_dir) environment variable) an alternative directory? No, this could lead to that you don't find the file that easily or in worst case the file is writeable for everyone, which could make your system easier to be compromised. > However, a possible update (of the system) could lead to the overwriting > of some of these files Most package managers do be able to detect if a file is modified and then just saves the new config with a postfix. If you create a new file, the package manager will know it and will not be trying to save over it unless the package for some reason would include a new config file named the same as your "random name", but then it would just add a postfix to the config file from the package. -- //Aho
[toc] | [prev] | [next] | [standalone]
| From | Custom Log <custom@log.abc> |
|---|---|
| Date | 2022-12-24 08:37 +0100 |
| Message-ID | <to6a6t$1665$1@gioia.aioe.org> |
| In reply to | #19215 |
Il 24/12/22 00:19, J.O. Aho ha scritto: > ... thanks for the info -----BEGIN PGP MESSAGE----- hQGMAyHa6HqE1N3qAQv/QomU8n0cDBQ05DPFeWfqZzr/XUMhX3KdNvNgMhvgWlrt WGmH7Vz2vTTumqQHTAVo1Vlzyvj5DZ+j+MzIDwns9xfWXc4MjFoJW+jCgZqr4mBx WkRGcJRVlVIMgednx9eojCFZHMIg6SKSF8KPvg48Bo4aqO96hPeaP8db0VzkQN4a X5ArvmODp6HPYZzHsyDpiGgxX3aYdpXMknpNCyAnm77SJ8JXIk/blLnG6reLz4o8 5VUAOgD2Pd0HIsebCBuGSY5ibHNJs2Ei+0AMmWqVUPqlpePtXs2+EBqQgVl0tRXz /TenC3iO/UDMjocWHbw12HfJA3WxhWIYBCOrPTowDVZtIUkdNGyMtG6jJtXkKJ7X fERMCKBcFD7MTduQV1OZghfA10OSXthd8Tmg+mvsDlFaJG24JoTe5+ZceaEXDfWr d53vTISp0kdu/U+yMRO5urVdYSEiFUPH2ECuZtgt0y/B82rR2HY1W32qlpsW05Vn ju6/ufXgh9HxkKWUkMSC0nEBFurEzABcTIvLMZpo0XXLcV9q2uRoRHG9PwmCyoZf AWJTA7K8ABHsp3q0RBmJnz7BrMzQSsJV6INk8fcnEEiu0zKCu46uSQxQ9ARBH9Hn uorrTANFMX6FlDsR+Oano76wOZxKTMc+sBtl8ezipDQQxQ== =widu -----END PGP MESSAGE-----
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.php
csiph-web