Is it possible to specify a working directory for the slave node started with slave:start/3 ? Currently it seems to be a user home directory, but a I’d like to specify a different one.
Best Regards,
Sergey
_______________________________________________________
CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
-----Original Message-----
From: Alex Shneyderman [mailto:a.shneyder...@gmail.com] Sent: Tuesday, October 30, 2012 12:22 PM
To: Zhemzhitsky Sergey
Subject: Re: [erlang-questions] slave node working directory
rpc:call(slave_node,file,set_cwd,["/tmp"]).
On Tue, Oct 30, 2012 at 9:16 AM, Zhemzhitsky Sergey <sergey_zhemzhit...@sberbank-cib.ru> wrote:
> Hello erlangers,
> Is it possible to specify a working directory for the slave node > started with slave:start/3 ? Currently it seems to be a user home > directory, but a I’d like to specify a different one.
> CONFIDENTIALITY NOTICE: This email and any files attached to it may be > confidential. If you are not the intended recipient you are notified > that using, copying, distributing or taking any action in reliance on > the contents of this information is strictly prohibited. If you have > received this email in error please notify the sender and delete this email.
<sergey_zhemzhit...@sberbank-cib.ru> wrote:
> Hi Alex,
> Thanks a lot. Unfortunately rpc:call does not work in my case as I have to start my slaves with a relative code search path specified with -pa option.
> Regards,
> Sergey
> -----Original Message-----
> From: Alex Shneyderman [mailto:a.shneyder...@gmail.com]
> Sent: Tuesday, October 30, 2012 12:22 PM
> To: Zhemzhitsky Sergey
> Subject: Re: [erlang-questions] slave node working directory
> rpc:call(slave_node,file,set_cwd,["/tmp"]).
> On Tue, Oct 30, 2012 at 9:16 AM, Zhemzhitsky Sergey <sergey_zhemzhit...@sberbank-cib.ru> wrote:
>> Hello erlangers,
>> Is it possible to specify a working directory for the slave node
>> started with slave:start/3 ? Currently it seems to be a user home
>> directory, but a I’d like to specify a different one.
>> CONFIDENTIALITY NOTICE: This email and any files attached to it may be
>> confidential. If you are not the intended recipient you are notified
>> that using, copying, distributing or taking any action in reliance on
>> the contents of this information is strictly prohibited. If you have
>> received this email in error please notify the sender and delete this email.
> Thanks a lot. Unfortunately rpc:call does not work in my case as I have to start my slaves with a relative code search path specified with -pa option.
I think this requirement should be satisfied outside the Erlang VM
itself. Setting up the environment parameters should be done by your
service management system.
For example systemd allows this (setting up working directory) as well
as setting many other necessary parameters right out of the box:
-----Original Message-----
From: Peter Lemenkov [mailto:lemen...@gmail.com] Sent: Tuesday, October 30, 2012 1:27 PM
To: Zhemzhitsky Sergey
Cc: Alex Shneyderman; erlang-questions Questions
Subject: Re: [erlang-questions] slave node working directory
2012/10/30 Zhemzhitsky Sergey <sergey_zhemzhit...@sberbank-cib.ru>:
> Hi Alex,
> Thanks a lot. Unfortunately rpc:call does not work in my case as I have to start my slaves with a relative code search path specified with -pa option.
I think this requirement should be satisfied outside the Erlang VM itself. Setting up the environment parameters should be done by your service management system.
For example systemd allows this (setting up working directory) as well as setting many other necessary parameters right out of the box:
_______________________________________________________
CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
