On Tuesday, January 08, 2013 21:40:50, Alan Jachimiak wrote: > Thanks for your help Chris! > > The logs I needed were in /var/log/dpkg.log.1
Good. > If your interested, here's the backstory: > After my apt-get upgrade, I had a couple websites that had broken links. > > In order to get human readable permalinks I had typed the needed code : > > try_files $uri $uri/ /index.php?q=$uri&$args; > > into the Nginx .vhost files manually. Apparently, these files were > rewritten/regenerated during the update. Concerning this, I'm going to babble about Debian packaging for a moment. Depending on *where* these configuration files are, that's not supposed to happen. /If/ these configuration files are in /etc/ then dpkg is supposed to /ask/ you before the configuration file is replaced or overwritten. [dpkg is supposed to do this directly, and thus this doesn't depend on whether the package uses debconf -- but it does depend on whether the configuration file has been /designated/ a config file as to whether this happens -- so it does matter how the source packge was built.] User-made (i.e. manual) configuration is supposed to be respected for /etc files. However, what a lot of packages do these days is move much of the configuration elsewhere (such as /lib/udev/rules.d/ a lot of which used to be in /etc/udev/rules.d/) such that in these locations the user is /not/ prompted concerning alteration of the configuration files, and the maintainer is thus free to overwrite them outright during upgrades. Usually the way this works is that /override/ files can be placed in /etc for the configuration that lives elsewhere but can be overwritten without prompting. That's thus the "it's okay, because" reasoning from the developer standpoint. Maybe this is in the package documention, and maybe it's not. There are long-standing "to-and-fro" arguments over which location (and thus situation) is better from the developer and user standpoints. > I was able to find that Ngninx was updated during the upgrade. > > Luckily, I've found that ispconfig3(link > <http://www.ispconfig.org/ispconfig-3/>) has a place in each website's > setup tab to store nginx directives. Ispconfig3 keeps these in a DB > and I think this will keep custom directives persistent through future > upgrades. Cool you've already answered what I was going to ask -- which is whether there is a "more persistent location" for customization for Ngnix. -- Chris -- Chris Knadle [email protected] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) Vassar College Jan 9 - High Performance Computing at a Small Scale Feb 6 - Raspberry Pi Mar 6 - 10th Anniversary Meeting - Linux where you least expect it
