| Author |
Message |
|
| Guest |
 Posted: Wed Aug 31, 2011 5:08 pm |
 |
|
|
Guest
|
When I do
> mnesia:stop().
I see this
=INFO REPORT==== 31-Aug-2011::19:03:57 ===
application: mnesia
exited: stopped
type: temporary
How can I get rid of this printout? I never want to see excess output
if the system has correctly done what I told it to do.
/Joe
_______________________________________________
erlang-questions mailing list
erlang-questions@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
Post received from mailinglist |
|
|
| Back to top |
|
| doubleyou |
| Posted: Wed Aug 31, 2011 6:27 pm |
|
|
|
User
Joined: 31 Dec 2009
Posts: 11
|
That's exactly what I want to do with rabbitmq erlang client as well 
On Wed, Aug 31, 2011 at 9:07 PM, Joe Armstrong <erlang@gmail.com> wrote:
> When I do
>
>> mnesia:stop().
>
> I see this
>
> =INFO REPORT==== 31-Aug-2011::19:03:57 ===
> |
|
|
| Back to top |
 
|
| Guest |
| Posted: Wed Aug 31, 2011 11:30 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Thu Sep 01, 2011 12:57 pm |
|
|
|
Guest
|
On Thu, Sep 1, 2011 at 1:30 AM, Joseph Norton <norton@lovely.email.ne.jp> wrote:
>
> Try the following ....
>
> $ erl -sasl errlog_type error
>
Thanks
Any idea if this also be done if I start with
$erl
I prefer to do *everything* by calling functions and not with command
line arguments
/Joe
> Joseph Norton
> norton@alum.mit.edu
>
>
>
> On Sep 1, 2011, at 3:27 AM, Dmitry Demeshchuk wrote:
>
>> That's exactly what I want to do with rabbitmq erlang client as well
>>
>> On Wed, Aug 31, 2011 at 9:07 PM, Joe Armstrong <erlang@gmail.com> wrote:
>>> When I do
>>>
>>>> mnesia:stop().
>>>
>>> I see this
>>>
>>> =INFO REPORT==== 31-Aug-2011::19:03:57 ===
>>> |
|
|
| Back to top |
|
| doubleyou |
| Posted: Thu Sep 01, 2011 12:59 pm |
|
|
|
User
Joined: 31 Dec 2009
Posts: 11
|
Perhaps application:set_env(errlog_type, error) ?
On Thu, Sep 1, 2011 at 4:57 PM, Joe Armstrong <erlang@gmail.com> wrote:
> On Thu, Sep 1, 2011 at 1:30 AM, Joseph Norton <norton@lovely.email.ne.jp> wrote:
>>
>> Try the following ....
>>
>> $ erl -sasl errlog_type error
>>
>
> Thanks
>
> Any idea if this also be done if I start with
>
> |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Sep 01, 2011 1:01 pm |
|
|
|
Guest
|
You need to do application:set_env(sasl, errlog_type, Type). The function with only 2 arguments will do it to the application where the current process belongs -- it won't work if you're not running as a part of the SASL process group. Force it with 3 arguments, where the first one is the name of the application.
--
Fred H |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Sep 01, 2011 3:05 pm |
|
|
|
Guest
|
Hi!
Usually you should avoid application:set_env/3 if it's not your own=20
application.
From=20the reference manual:
"Warning:
Use this function only if you know what you are doing, that is, on=
=20
your own applications. It is very application and configuration parameter=
=20
dependent when and how often the value is read by the application, and=20
careless use of this function may put the application in a weird,=20
inconsistent, and malfunctioning state."
Perhaps it works now, depending how SASL handles the parameter, but=20
that might change at any given time without a warning.
Best regards,
Niclas @ Erlang/OTP
On Thu, 1 Sep 2011, Fr=E9d=E9ric Trottier-H=E9bert wrote:
> You need to do application:set_env(sasl, errlog_type, Type). The=20
> function with only 2 arguments will do it to the application where the=20
> current process belongs -- it won't work if you're not running as a part=
=20
> of the SASL process group. Force it with 3 arguments, where the first=20
> one is the name of the application.
>
> --
> Fred H=E9bert
> http://www.erlang-solutions.com
>
>
>
> On 2011-09-01, at 08:59 AM, Dmitry Demeshchuk wrote:
>
>> Perhaps application:set_env(errlog_type, error) ?
>>
>> On Thu, Sep 1, 2011 at 4:57 PM, Joe Armstrong <erlang@gmail.com> wrote:
>>> On Thu, Sep 1, 2011 at 1:30 AM, Joseph Norton <norton@lovely.email.ne.j=
p> wrote:
>>>>
>>>> Try the following ....
>>>>
>>>> $ erl -sasl errlog_type error
>>>>
>>>
>>> Thanks
>>>
>>> Any idea if this also be done if I start with
>>>
>>> $erl
>>>
>>> I prefer to do *everything* by calling functions and not with command
>>> line arguments
>>>
>>> /Joe
>>>
>>>
>>>
>>>
>>>> Joseph Norton
>>>> norton@alum.mit.edu
>>>>
>>>>
>>>>
>>>> On Sep 1, 2011, at 3:27 AM, Dmitry Demeshchuk wrote:
>>>>
>>>>> That's exactly what I want to do with rabbitmq erlang client as well =
>>>>>
>>>>> On Wed, Aug 31, 2011 at 9:07 PM, Joe Armstrong <erlang@gmail.com> wro=
te:
>>>>>> When I do
>>>>>>
>>>>>>> mnesia:stop().
>>>>>>
>>>>>> I see this
>>>>>>
>>>>>> =3DINFO REPORT=3D=3D=3D=3D 31-Aug-2011::19:03:57 =3D=3D=3D
>>>>>> application: mnesia
>>>>>> exited: stopped
>>>>>> type: temporary
>>>>>>
>>>>>> How can I get rid of this printout? I never want to see excess outpu=
t
>>>>>> if the system has correctly done what I told it to do.
>>>>>>
>>>>>> /Joe
>>>>>> _______________________________________________
>>>>>> erlang-questions mailing list
>>>>>> erlang-questions@erlang.org
>>>>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best regards,
>>>>> Dmitry Demeshchuk
>>>>> _______________________________________________
>>>>> erlang-questions mailing list
>>>>> erlang-questions@erlang.org
>>>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Best regards,
>> Dmitry Demeshchuk
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@erlang.org
>> http://erlang.org/mailman/listinfo/erlang-questions
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions
>
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Sep 01, 2011 3:09 pm |
|
|
|
Guest
|
True, but otherwise, the call to application:set_env/2 will just not work. Still a good warning to give, yes.
--
Fred H |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Sep 01, 2011 4:54 pm |
|
|
|
Guest
|
I think that, as long as you call application:set_env(A,K,V) before you start the application A, you're probably safe. However, for some applications, this may be hard to accomplish. For example, if you use -boot start_sasl, then sasl will have started by the time you get to the interactive prompt. Maybe building your own boot script that configures this would be a suitable alternative? That would also work for non-interactive nodes (auto-start in /etc/init.d, etc)
Sincerely,
Jw
--
Americans might object: there is no way we would sacrifice our living standards for the benefit of people in the rest of the world. Nevertheless, whether we get there willingly or not, we shall soon have lower consumption rates, because our present rates are unsustainable.
2011/9/1 Frédéric Trottier-Hébert <fred.hebert@erlang-solutions.com (fred.hebert@erlang-solutions.com)>
Quote: True, but otherwise, the call to application:set_env/2 will just not work. Still a good warning to give, yes.
--
Fred Hébert
http://www.erlang-solutions.com
On 2011-09-01, at 11:04 AM, Niclas Eklund wrote:
>
> Hi!
>
> Usually you should avoid application:set_env/3 if it's not your own application.
>
> From the reference manual:
>
> "Warning:
> Use this function only if you know what you are doing, that is, on your own applications. It is very application and configuration parameter dependent when and how often the value is read by the application, and careless use of this function may put the application in a weird, inconsistent, and malfunctioning state."
>
> Perhaps it works now, depending how SASL handles the parameter, but that might change at any given time without a warning.
>
> Best regards,
>
> Niclas @ Erlang/OTP
>
> On Thu, 1 Sep 2011, Frédéric Trottier-Hébert wrote:
>
>> You need to do application:set_env(sasl, errlog_type, Type). The function with only 2 arguments will do it to the application where the current process belongs -- it won't work if you're not running as a part of the SASL process group. Force it with 3 arguments, where the first one is the name of the application.
>>
>> --
>> Fred Hébert
>> http://www.erlang-solutions.com
>>
>>
>>
>> On 2011-09-01, at 08:59 AM, Dmitry Demeshchuk wrote:
>>
>>> Perhaps application:set_env(errlog_type, error) ?
>>>
>>> On Thu, Sep 1, 2011 at 4:57 PM, Joe Armstrong <erlang@gmail.com (erlang@gmail.com)> wrote:
>>>> On Thu, Sep 1, 2011 at 1:30 AM, Joseph Norton <norton@lovely.email.ne.jp (norton@lovely.email.ne.jp)> wrote:
>>>>>
>>>>> Try the following ....
>>>>>
>>>>> $ erl -sasl errlog_type error
>>>>>
>>>>
>>>> Thanks
>>>>
>>>> Any idea if this also be done if I start with
>>>>
>>>> $erl
>>>>
>>>> I prefer to do *everything* by calling functions and not with command
>>>> line arguments
>>>>
>>>> /Joe
>>>>
>>>>
>>>>
>>>>
>>>>> Joseph Norton
>>>>> norton@alum.mit.edu (norton@alum.mit.edu)
>>>>>
>>>>>
>>>>>
>>>>> On Sep 1, 2011, at 3:27 AM, Dmitry Demeshchuk wrote:
>>>>>
>>>>>> That's exactly what I want to do with rabbitmq erlang client as well
>>>>>>
>>>>>> On Wed, Aug 31, 2011 at 9:07 PM, Joe Armstrong <erlang@gmail.com (erlang@gmail.com)> wrote:
>>>>>>> When I do
>>>>>>>
>>>>>>>> mnesia:stop().
>>>>>>>
>>>>>>> I see this
>>>>>>>
>>>>>>> =INFO REPORT==== 31-Aug-2011::19:03:57 ===
>>>>>>> application: mnesia
>>>>>>> exited: stopped
>>>>>>> type: temporary
>>>>>>>
>>>>>>> How can I get rid of this printout? I never want to see excess output
>>>>>>> if the system has correctly done what I told it to do.
>>>>>>>
>>>>>>> /Joe
>>>>>>> _______________________________________________
>>>>>>> erlang-questions mailing list
>>>>>>> erlang-questions@erlang.org (erlang-questions@erlang.org)
>>>>>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best regards,
>>>>>> Dmitry Demeshchuk
>>>>>> _______________________________________________
>>>>>> erlang-questions mailing list
>>>>>> erlang-questions@erlang.org (erlang-questions@erlang.org)
>>>>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Dmitry Demeshchuk
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@erlang.org (erlang-questions@erlang.org)
>>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@erlang.org (erlang-questions@erlang.org)
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
_______________________________________________
erlang-questions mailing list
erlang-questions@erlang.org (erlang-questions@erlang.org)
http://erlang.org/mailman/listinfo/erlang-questions
Post received from mailinglist |
|
|
| Back to top |
|
| uwiger |
| Posted: Thu Sep 01, 2011 5:06 pm |
|
|
|
User
Joined: 03 Jul 2006
Posts: 604
Location: Sweden
|
For those who want to change application environment variables in running systems, I recommend taking a look at gproc's support for environment variables.
Basically, gproc helps with a few different problems with configuration environments:
- there are so many ways to specify parameters: unix env vars, OTP env vars, mnesia, |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Sep 01, 2011 8:24 pm |
|
|
|
Guest
|
Does it count to put it in an app.config file that is referenced with $erl -config var/app ?
yeah, essentially the same thing, but easier to version control and you can be sure its read at startup, which seems to be the issue mentioned to do with application:set_env/3
Sam
On Thu, Sep 1, 2011 at 1:57 PM, Joe Armstrong <erlang@gmail.com (erlang@gmail.com)> wrote:
Quote: On Thu, Sep 1, 2011 at 1:30 AM, Joseph Norton <norton@lovely.email.ne.jp (norton@lovely.email.ne.jp)> wrote:
>
> Try the following ....
>
> $ erl -sasl errlog_type error
>
Thanks
Any idea if this also be done if I start with
$erl
I prefer to do *everything* by calling functions and not with command
line arguments
/Joe
> Joseph Norton
> norton@alum.mit.edu (norton@alum.mit.edu)
>
>
>
> On Sep 1, 2011, at 3:27 AM, Dmitry Demeshchuk wrote:
>
>> That's exactly what I want to do with rabbitmq erlang client as well
>>
>> On Wed, Aug 31, 2011 at 9:07 PM, Joe Armstrong <erlang@gmail.com (erlang@gmail.com)> wrote:
>>> When I do
>>>
>>>> mnesia:stop().
>>>
>>> I see this
>>>
>>> =INFO REPORT==== 31-Aug-2011::19:03:57 ===
>>> application: mnesia
>>> exited: stopped
>>> type: temporary
>>>
>>> How can I get rid of this printout? I never want to see excess output
>>> if the system has correctly done what I told it to do.
>>>
>>> /Joe
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@erlang.org (erlang-questions@erlang.org)
>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>
>>
>>
>>
>> --
>> Best regards,
>> Dmitry Demeshchuk
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@erlang.org (erlang-questions@erlang.org)
>> http://erlang.org/mailman/listinfo/erlang-questions
>
>
_______________________________________________
erlang-questions mailing list
erlang-questions@erlang.org (erlang-questions@erlang.org)
http://erlang.org/mailman/listinfo/erlang-questions
--
Samuel Elliott
sam@lenary.co.uk (sam@lenary.co.uk)http://lenary.co.uk/
+44 (0)7891 993 664
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Sep 02, 2011 4:02 pm |
|
|
|
Guest
|
On 09/01/2011 02:30 AM, Joseph Norton wrote:
>
> Try the following ....
>
> $ erl -sasl errlog_type error
>
This does not seem to work for me with R14B02 and I have others confirm
under R14B03.
All of mnesia:stop(), application:stop(mnesia) and
error_logger:info_msg("test") print info reports.
Any ideas why?
Thanks
/Ignas
_______________________________________________
erlang-questions mailing list
erlang-questions@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Sep 04, 2011 3:33 am |
|
|
|
Guest
|
I was mistaken.
This option seems to only disable SASL progress reports. "error reports" seems to include info level log events as well.
Excerpt from sasl modules documentation:
errlog_type = error | progress | all <optional>
Restricts the error logging performed by the specified sasl_error_logger to error reports, progress reports, or both. Default is all.
Excerpt from lib/sasl/src/sasl.erl module:
type(error) -> error;
type(progress) -> progress;
type(_) -> all.
Joseph Norton
On Sep 3, 2011, at 1:02 AM, Ignas Vy |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
