[erlang-questions] RE On node disconnections

Olivier BOUDEVILLE olivier.boudeville@REDACTED
Wed Apr 10 15:38:26 CEST 2013

Hi Vance,

Thanks for your answer!

Indeed by running:

        run_erl -daemon /tmp/my-pipe  . "exec erl [...]"

Then waiting for the pipes to be created, then running:

        echo "my_module:my_function()." >> /tmp/my-pipe.w

I could run a code that resists 'no_connection' exceptions and does not 
need the user to type anything in the shell.

Adding a "tail -f erlang.log.1" pretty recreates what the 'init' module 
gives out-of-the-box (but with an exception-safe VM).

A minor question: in run-erl.log a line tells "Client expected on FIFO 
/tmp/my-pipe.r, but can't open"; I assume this is not a real problem? 
I would have imagined that I could read this pipe (with a tail or a cat) 
to monitor the program console outputs, possibly instead of relying on 
erlang.log.1 for that. Maybe run_erl prevents that. Actually a tee on this 
pipe could have been useful, as for longer outputs the newer logs will be 
written in erlang.log.2, which makes a console monitoring tricky ("tail -f 
erlang.log.1" having to become "tail -f erlang.log.2" etc.)

Thanks again,
Best regards,

Olivier Boudeville

EDF R&D : 1, avenue du Général de Gaulle, 92140 Clamart, France
Département SINETICS, groupe ASICS (I2A), bureau B-226
Office : +33 1 47 65 59 58 / Mobile : +33 6 16 83 37 22 / Fax : +33 1 47 
65 27 13

10/04/2013 11:34

Re: [erlang-questions] RE On node disconnections

On Wed, Apr 10, 2013 at 11:27:52AM +0200, Olivier BOUDEVILLE wrote:
}  So: what could be the solution to run a VM as batch (without the 
}  interactive shell) while still being able to overcome errors (such as 
}  'noconnection')?



Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.

This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or virus-free.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130410/6173640b/attachment.htm>

More information about the erlang-questions mailing list