|
From: <nic...@uk...> - 2005-12-08 03:11:28
|
>> I am thinking of changing this behavior for the 3.2.0 release so that >> the RUN_AS_USER setting is always used. Excellent >> I take it you agree with this? Yep. 100% Most of our usage of RUN_AS_USER is so that the process has the correct permissions. It wont work running as anyone else (except root - which we dont have access to) >> Do you see any potential problems? Havent been able to think of any at all - hence the email :-) On a different but related topic - what else is going into the next release? -Nick Internet le...@ta...@lists.sourceforge.net - 08/12/2005 02:53 Please respond to wra...@li... Sent by: wra...@li... To: wrapper-user cc: Subject: Re: [Wrapper-user] RUN_AS_USER question Nick, The thinking here was that running in console mode would mainly be done by developers where as it would be run as a daemon process when being run as the specific user. I have actually been reconsidering this as of late. If I have a user "myapp" which the app is being run as, then I attempt to run it in console mode as a test then several files will be created by "root" rather than "myapp". If I then go back and start the application as a daemon process, the files created in the previous run will not be able to be accessed as they were created as "root"... I am thinking of changing this behavior for the 3.2.0 release so that the RUN_AS_USER setting is always used. I take it you agree with this? Do you see any potential problems? I doubt that anyone will complain about this as anyone who had been taking advantage of the old behavior would likely have been running into the problem that I mentioned above. Cheers, Leif nic...@uk... wrote: > What is the rationale behind RUN_AS_USER only being used when starting the > wrapper? > > Why not when running in console - or when stopping? > > Given that wrapper seems to be a very well-thought out app I imagine there > is a good reason - I am just not seeing it... > > -Nick > > > > This message and any attachments (the "message") is > intended solely for the addressees and is confidential. > If you receive this message in error, please delete it and > immediately notify the sender. Any use not in accord with > its purpose, any dissemination or disclosure, either whole > or partial, is prohibited except formal approval. The internet > can not guarantee the integrity of this message. > BNP PARIBAS (and its subsidiaries) shall (will) not > therefore be liable for the message if modified. > > ********************************************************************************************** > > BNP Paribas Private Bank London Branch is authorised > by CECEI & AMF and is regulated by the Financial Services > Authority for the conduct of its investment business in > the United Kingdom. > > BNP Paribas Securities Services London Branch is authorised > by CECEI & AMF and is regulated by the Financial Services > Authority for the conduct of its investment business in > the United Kingdom. > > BNP Paribas Fund Services UK Limited is authorised and > regulated by the Financial Services Authority > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |