Hello all, I am running 14.2 and just used slackpkg to upgrade to the 4.4.111 kernel and latest bind package. After I ran this I - admittedly in error - selected to use the new config files. I do not use bind services so did not think would hurt. In any case, after reboot, my sugarcrm quit working. I traced back to missing information in httpd.conf and etc/php.ini. Neither of the file dates were changed (ls -tl) I am just curious why these files were affected at all for the kernel/bind updates and more so why the file date would not have been changed to today's date.

These files were not affected by the recent updates, but php was last updated on Fri Oct 27 20:34:35 UTC 2017 and httpd on Wed Oct 25 19:09:26 UTC 2017.

So if something is missing in these files this has been since when you applied these updates or before, no later (unless you edited these files yourself later).

I'd check if there has been a change in sugarcrm instead.

That is the crazy part, those config files were dated 10/26 but they were missing some config settings - i.e. the server IP address in httpd.conf. Sugar was working up to the point I ran the most recent updates. Could it be possible that all the config files were updated because I selected use new on this update?

Just to confirm, these are the upgrades I made this morning.

-rw-r--r-- 1 root root 3477928 Jan 18 06:50 kernel-source-4.4.111-noarch-1
-rw-r--r-- 1 root root 253536 Jan 18 06:48 kernel-modules-4.4.111-x86_64-1
-rw-r--r-- 1 root root 974 Jan 18 06:48 kernel-huge-4.4.111-x86_64-1
-rw-r--r-- 1 root root 25089 Jan 18 06:48 kernel-headers-4.4.111-x86-1
-rw-r--r-- 1 root root 978 Jan 18 06:48 kernel-generic-4.4.111-x86_64-1
-rw-r--r-- 1 root root 60683 Jan 18 06:48 kernel-firmware-20180104_65b1c68-no
-rw-r--r-- 1 root root 14070 Jan 18 06:47 bind-9.10.6_P1-x86_64-1_slack14.2

Exactly that happened.
If slackpkg asks you what to do with the .new files, you should always determine if that can be done using the interactive process (pick option 'p') and then use the diff menu to view the differences to your original configuration files. The Slackware package tools did not overwrite your configuration, with good reason. You overwrote your customized httpd.conf and php.ini when you told slackpkg to use all the .new files it found.
Note that your originals should still be present on the system, they will have been suffixed with ".orig". Moving them back in place will solve your issue but please spend a little time comparing the old and the new files to see if there's anything in the new files you need to adopt in your original files.

It would be good if you read this: https://docs.slackware.com/howtos:sl...using_slackpkg

2 members found this post helpful.

Thank you for the explanation - I was not aware that slackpkg would do this. I be more careful in future.