Oh, on personal ramblings: I hate the way gmail sort my inbox! See my comments below.
On 5/11/06, Gabriel Falkenberg <[EMAIL PROTECTED]> wrote: > Ok, I have solved the problem... That the log-files weren't even created > should have made me realize that the problem had to do with file-access > permissions. When I started the app as a service it got other privileges > than when I started it at the prompt and that was why the app didn't start, > because it couldn't create the log files... > I guess I will need to check for win2k, but for XP the context where each service gets created and runs under SYSTEM account, which often have wide privileges around files. You could change that behavior from the Services applet in administrative tools. > > When running Mongrel as a service you have to think about what permissions > the service is going to get. If the service doesn't have write-access to the > log-files in the gem's bin-directory (something like: > C:\ruby\lib\ruby\gems\1.8\gems\mongrel-0.3.12.4-mswin32\bin) it won't be > able to start and you won't get any log files that tells you why. > [snip] > Also remember that rails needs to be able to write to certain directories > like the log-directory (railsapp/log) and the directories beneath > railsapp/tmp/ > The logs file aren't created inside the gem, instead they will get created in the log folder of the rails application. Please check the permissions of these folders too. > > What do you think? > As my previous email, I'll suggest test the daemon_test.rb shiped with win32-service. That writes information to c:\test.log, which require privileges. Please check that and let me know on which account the service start (you could check with task manager). Anyway, glad to hear that it worked ;-) Later, Luis Lavena _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
