-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/09/2013 03:13 AM, M Saunders wrote:
which has some useful tips. But it'd be interesting to hear from people running Arch on production servers, how well it works for them and what (if any) problems they've faced.
Mine is pretty small scale as "production" goes. But my overall experience running Arch on a server (I currently actually have two of them) for at least a couple years now is that Arch tends to be stable without doing anything special. The one time I got burned was on the latest consolidation to /usr/bin, where some critical postfix file permissions were not preserved--and the nature of the problem was such that, at least in my situation, it didn't show up for hours after. The fix was easy enough; postfix has a command option just for this situation, and a new version of the postfix package was available within a few hours that I assume would have fixed the problem by itself had I waited just that length of time before doing the upgrade. So the one bit of advice I would offer probably won't be shocking: whenever an upgrade comes down that seems critical, it is probably prudent to just wait a day. - -- David Benfell / benfell@parts-unknown.org Please see https://parts-unknown.org/node/2 for GnuPG information (or the attachment you don't understand) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR3LiUAAoJELJhbl/uPb4S6RsQAIaRG6OjYuRlqePu1egVKfVb uPJ6d/fyNklJC6xfouHVI23RTDUUdEwZBNwH3sx0pUjBXjNYAXjXLSgdSVcsogFX nq0Ores/7MdjlOeAHZzGCNsXQ61u37WC02xFVngB1uUhaOsPHiDfo4SGKvkrt54k k4LhEVpsoAoaDZcuOZzPl3BGllvJouopSvpAsyNJFvIMxBKPfC0+UzjSkzqsutbg AesHzk3lmeEwL7VCOA3hwjeNHpBMRpAdvsoN2SE0X26KKQgNsp+lKVhWJD94v091 DxjUpgRbxeVLvD5YToQQZ0L9AHFlAPfRESE8nlTHSPHbkp9Yoa0b6qVEO3ryviGG s65uCvU+7H8ZPZBs4WY4ucJxiJDWLhhQJeAYojQbO9FD/5HI61gmy0dF63BSwojS mjgVm2ajOJ2DWyHNvox6SMRfHCnZojKbSEeOyQyUn6e1wyMCXkYz0GE832LbXaKd rGF55fW6fIntT/nCl/1acsdLEYVSm9HIMJToogh7TNltLOOMSejwLI60dGf7K6EG yuO0kc1SjvagJ0uDMnis+N05gXSLMNomdUjZNW+RKPaqbo1UahgoozmDEmK2rO5S SdOBdZyAayfeaIbUld7bHOWDdwb78v+ytOY36j73ZQq0qPty9FR8s3BLrO6hcOw1 YIEmGXlC87r7WlbFYsfV =cLql -----END PGP SIGNATURE-----