Custom Query (196 matches)

On conan-obrien

/etc/cron.daily/logrotate:
kill: 91: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
error: error running non-shared postrotate script for /var/log/conserver/bees-knees.log of '/var/log/conserver/*.log '
kill: 91: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
error: error running non-shared postrotate script for /var/log/conserver/miracle-cure.log of '/var/log/conserver/*.log '
kill: 91: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
error: error running non-shared postrotate script for /var/log/conserver/server.log of '/var/log/conserver/*.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

The trouble is that /var/run/conserver.pid no longer has a pid in it. But this is not the case for david-letterman. Quite vexing.

Most of our software supports upgrading by switching to a newer tag, updating, and possibly running an upgrade databases script. If we install a SVN (or whatever VCS) working copy rather than extracting a tarball, users can upgrade their own installs easily. Our auto-upgrade process should also become easier.

For SVN, we can merely generate a tarball with the .svn directories and keep our existing auto-install (and to some extent, auto-upgrade) infrastructure. I suspect this will work with all other VCSes.

There are also packages such as Django that very much recommend installing HEAD rather than a tarballed release, so having an infrastructure that will deal with VCSes will make it easier to support such packages.

Django is popular and cool. kcarnold has expressed interest in helping make a Django installer, perhaps akin to nelhage's Jifty installer. Since Django does not have external dependencies outside stock Python, this should be easy.