On 10/4/07, eschurig <[EMAIL PROTECTED]> wrote: > > Thank you so much, you've made my day. Slimserver is back up. Instead > of deleting the files I moved them to a backup directory in case I > wanted to look at the log and startup files you talked about. I > thought slimserver was stopped but as fast as the files were eliminated > by the move, they reappeared and the slimserver was up and running.
Great news! I guess a lingering question would be: what did I do wrong to begin > with? I did stop slimserver before udating the software. Aptitude > seemed to carry on the update smoothly. I don't remember deleting the > database files last time I upgraded. Did the database change > significantly in a way that would cause slimserver to lock up with the > old database files in place? There's probably nothing that you did wrong. It's quite possible that if you had upgraded individually from 6.5 to 6.5.1, 6.5.2, 6.5.3 and 6.5.4 that things might have worked out. I doubt anyone is testing the 6.5.0 to 6.5.4Debian migration. I suspect that if any testing of this is done at all that it is from the previous version only (i.e. 6.5.3 to 6.5.4). I think there's a bit of an assumption that those using Linux are a bit more technically inclined and are able to solve some problems by themselves or use the forums to ask for help (as you did). I guess I personally feel lucky that we get .deb packages at all. :-) Ben
_______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
