Rob, The issue here, as you have correctly pointed out, is that the service control commands are not passed to the nxlog process if it is started via a service wrapper. As such, I think it can't be shut down gracefully, which is needed to flush buffers and write the configcache.dat containing eventlog/file positions.
Regards, Botond On Thu, 17 Jul 2014 19:28:23 +0000 nx...@robajz.info wrote: > Apologies for double posting, I just re-discovered nssm: > http://nssm.cc/usage - it has a priority setting for the process. > Question remains please concerning service signals and graceful shutdown. > Thanks, Rob > > On 07/17/14 19:18, nx...@robajz.info wrote: > > Hi Botond, thanks for the answer. > > > > I have seen these techniques with task manager and unfortunately it will > > not fly on production serves for multiple reasons (technical and > > operational). > > > > I'm thinking now of service wrapper like srvany that might allow me to > > do that or perhaps I might just write one in c#. Would there be much > > concern in nxlog.exe regarding service signals and how about shutting > > down gracefully if I wrap the process say with srvany and cmd script or > > with custom c# service? > > > > Thanks and regards, Rob > > > > > > On 07/17/14 13:09, nxlog-ce-users-requ...@lists.sourceforge.net wrote: > >> Message: 1 > >> Date: Thu, 17 Jul 2014 10:37:49 +0200 > >> From: Botond Botyanszki <b...@nxlog.org> > >> Subject: Re: [nxlog-ce-users] Change nxlog process priority > >> To: nxlog-ce-users@lists.sourceforge.net > >> Message-ID: <20140717103749.792ec84d@mephisto> > >> Content-Type: text/plain; charset=US-ASCII > >> > >> Hi Rob, > >> > >> Not sure what's the best way to do this on windows either but there are > >> tools which could work, see this for example: > >> http://www.askvg.com/how-to-permanently-set-process-priority-in-windows-task-manager/ > >> YMMW. > >> > >> Regards, > >> Botond > >> > >> On Thu, 10 Jul 2014 18:13:46 +0000 > >> nx...@robajz.info wrote: > >> > >>> Hi, > >>> > >>> >From my localhost UDP load testing it became apparent that to avoid > >>> packet drop under heavy load, the receiving process needs to run with > >>> higher process priority than the senders. This ensures that it has the > >>> CPU cycles to handle all the input where it has to compete with the > >>> senders. > >>> > >>> Local UDP sink is part of my design and hence I'm wondering if there's > >>> some simple way to prop the process priority of nxlog on windows > >>> (windows 2008 server actually). I wouldn't fancy some brutal external > >>> scripts but well if it hs to be... Wish it was linux easy. > >>> > >>> Thanks a lot, Rob > >>> > >>> > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > nxlog-ce-users mailing list > nxlog-ce-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
