Stuff

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

On a slightly different note, I've been checking my logs lately and in the past several weeks I've had to keep restarting slashd as it has been hanging during freshenup.pl (usually the last line in slashd.log is something like "Updating 03/04/22/1551213". Anyone else have this happen? It happens at least once a day now, I have had to schedule a cron job to restart slashd every hour. Slash 2.2.6

I've been running the same code for about a year, the only thing I did recently was upgrade the kernel (RedHat):2.

I know vlad's not recommending it, they had all *sorts* of problems doing it.

But there are quite a few people who didn't have such problems that vlad and his crew did.

I did my 4 or 5 sites, in roughly a week, tinkering with it in the evenings. Most of my time was spent meshing changes that I'd done to both the slash src and my plugins. Templates were a joy to do, but for each site it only took about a half hour to diff the template changes and reimplement them into the newly upgraded sites.

Thanks for your perspective and good to hear it went well for you. Approx. 1 week for you and Vlad's approx. 1 week really isn't too bad. I think it took me several months to initially get Slash running smoothly. This was version 1.0.4 and most major problems have been worked out now it seems.

The transitions from 1.0x to 2.0 and also from 2.0 to 2.2 went well, thanks to the Slash crew's upgrade scripts. I definitely want to move up to the latest, it is just a question of when to pull the trigger and start the process of moving to the latest version. I've got the dev box ready, so it should be fairly soon. Good to know others have already been through a similar scenario.