Thank you very much for your cooperation and sooner response,
>services run under windows (32bits) with "services.exe" as parent >process. Could you use ProcessExplorer [1] to check other services >working and who its process parent? Yes, as same as Win32, "services.exe" is the parent process of "svchost.exe", "snmp.exe" , "mysqld-nt.exe", "VMwareService.exe", etc. and only "services.exe" and "svchost.exe" is 64-bit image. I'm sorry that "service.exe" in the subject is a TYPO. >I attached a 7z file with proc_info.exe, which will test if the WinAPI >used works. Please run it front the command line, the expected output >will be: The result is : this process (PID, name): 2192, proc_info.exe parent process (PID, name): 3024, <unknown> "<unknown>" is the error or the warning word returned by "_process_name" function of ServiceFB. and "_process_name" function uses Win32API "HANDLE" typedef via FreeBasic libs, and the size of HANDLE of Win32API differs from the other one of Win64API. so, if "proc_info.exe" is getting its process name without its PID, I guess that the root of this compatibility problem will exist around here. #if so, Perhaps I should not be bothering you with this... > If that works, that means the Services and Controller application > (services.exe) is named differently under x64, or due 32bits > compatibility run as child process of _another_ process :-P > With that information I could patch mongrel_service current version :-) mmm, How about these results? Sincerely, _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
