<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>That's correct for me - given it wasn't blindingly obvious how to change this in rebar3 (ie, under either the "getting started" or "configuration" section of documentation), it quickly becomes one of those "do I really want to change this and deal with being
non-standard"? Those sorts of situations generally outweigh filesystem standards that a particular product may or may not use.<br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> erlang-questions-bounces@erlang.org <erlang-questions-bounces@erlang.org> on behalf of Tristan Sloughter <t@crashfast.com><br>
<b>Sent:</b> Thursday, 16 June 2016 12:27:08 AM<br>
<b>To:</b> erlang-questions@erlang.org<br>
<b>Subject:</b> Re: [erlang-questions] Pipes - systemd</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Yea, I assume people are using /tmp because rebar 2.x and relx (based on<br>
the script from rebar 2.x) uses /tmp in the release start script.<br>
<br>
I am going to update the relx script to use /var/run by default, which<br>
will also update rebar3.<br>
<br>
-- <br>
Tristan Sloughter<br>
t@crashfast.com<br>
<br>
On Wed, Jun 15, 2016, at 09:21 AM, Garrett Smith wrote:<br>
> Once you fix that behavior, you'll probably be up against others that<br>
> sprout up in time. Don't use /tmp for process files, unless they're ad<br>
> hoc or short lived. As others have said /var/run or /run is generally<br>
> where you want those to land.<br>
> <br>
> <a href="https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard">https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard</a><br>
> <br>
> On Mon, Jun 13, 2016 at 8:52 PM, Technion <technion@lolware.net> wrote:<br>
> > Hi,<br>
> ><br>
> ><br>
> > I've had a lot of frustrating times with this issue and wanted to mention it<br>
> > before anyone else does.<br>
> ><br>
> ><br>
> > Specifically, my erl pipes kept getting deleted, meaning you couldn't<br>
> > attach, or cleanly shutdown services.<br>
> ><br>
> ><br>
> > After far too long, I've tracked this to a new systemd service, and found<br>
> > the fix involves editing this file:<br>
> ><br>
> ><br>
> > /usr/lib/tmpfiles.d/tmp.conf<br>
> ><br>
> ><br>
> > And telling it not to apply the default ten day lifetime on this folder:<br>
> ><br>
> ><br>
> > x /tmp/erl_pipes<br>
> ><br>
> ><br>
> > I'm expecting that will sort it out (although I know now I need ten days to<br>
> > tell).<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > erlang-questions mailing list<br>
> > erlang-questions@erlang.org<br>
> > <a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> ><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> erlang-questions@erlang.org<br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
_______________________________________________<br>
erlang-questions mailing list<br>
erlang-questions@erlang.org<br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</div>
</span></font>
</body>
</html>