On Monday, 17 February 2014 15:55:45 UTC-7, Volker Braun wrote:
>
> I had some troubles running the buildbot slave through systemd. You
> service will be selinux confined and some doctests with external programs
> fail on Fedora 20. Nothing particularly important afair.
>
Somewhat (un)related -
I had some troubles running the buildbot slave through systemd. You service
will be selinux confined and some doctests with external programs fail on
Fedora 20. Nothing particularly important afair.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group
On 2/17/14 11:09 AM, William Stein wrote:
On Mon, Feb 17, 2014 at 9:07 AM, Jason Grout
wrote:
On 2/15/14 11:44 PM, Henry de Valence wrote:
This approach requires systemd and is Linux-specific, but as every major
Linux distribution is either using systemd now or plans to move to it in
the futu
On Mon, Feb 17, 2014 at 9:07 AM, Jason Grout
wrote:
> On 2/15/14 11:44 PM, Henry de Valence wrote:
>>
>> This approach requires systemd and is Linux-specific, but as every major
>> Linux distribution is either using systemd now or plans to move to it in
>> the future, it seems like it might be wor
On 2/15/14 11:44 PM, Henry de Valence wrote:
This approach requires systemd and is Linux-specific, but as every major
Linux distribution is either using systemd now or plans to move to it in
the future, it seems like it might be worthwhile for Sage to ship
systemd .service files for Linux users.
Henry de Valence writes:
> Hi all,
>
> while looking at the SAGE FAQ here [1], I noticed the link to Trac #381 [2]
> (the link is broken, on the FAQ page, though).
>
> One option which is not mentioned, but which is extremely convenient,
> is to run Sage using a systemd user session. The Arch Linu
