On Mon, Sep 6, 2010 at 1:36 AM, Chris Brown <chr...@mmworks.com.au> wrote: [...] > The logfile contains the following ... > > /usr/local/sbin/gearmand.exe: error while loading shared libraries: > cygevent-1-4-2.dll: cannot open shared object file: No such file or directory > > Can anyone explain why gearmand.exe runs from the commandline but not as a > service?
I'd guess that the DLL search path is different when you're invoking it from the cygwin command line and when it's getting run by the NT service code. This isn't a libevent issue per se. To get you started, you can check out the msdn article at http://msdn.microsoft.com/en-us/library/7d83bc18(VS.80).aspx , and try to figure out which of these options is under your control when running as a service. Alternatively, if disk space isn't too tight, you could just link your program against libevent statically, and ignore the DLL issues completely. > I've tried running the service using my login credentials (just in case there > is something about my environment I'm overlooking) but this fails with a > login error. > > Also, the cygevent-1-4-2 dlls are in /usr/local/bin; is this correct? Somebody else might be able to answer this one; I haven't used cygwin in ages. Re the issues in your other message: it looks like we've got some timing/DNS portability issues on cygwin. None of them look like they're going to break typical programs, but it would be neat if somebody wanted to track them down sometime and fix them. We've been doing our windows testing on mingw and msvc, but this is supposed to be a portability library after all. hth, -- Nick *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.
