sourcing perlbrew bashrc does'nt give you anything but the advantage to `use` a different version on-the-fly. It is unlkely that you need to do so when launching the app daemon. I would simply put the desired perlbrew-ed version of perl in the $PATH when launching the app daemon.

To automatically do that when rebooting the machine, create a shell script as a wrapper that modify the PATH first, then launch the app, and invoke the wrapper script from crontab (with @reboot time) or init.d.

perlbrew really does not have to be involved unless it is required to run app with multiple versions of perl. Even so, writing multiple wrapper scripts cannot be too difficult. :)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.