ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Installing context on a web server
Date: Fri, 19 Jul 2013 15:45:36 +0200	[thread overview]
Message-ID: <CALBOmsYmkiVuDONnE1n6Kh+C4Pqb6JuEGV_8wQm=tU1oM13Zag@mail.gmail.com> (raw)
In-Reply-To: <51E93F28.9040606@stdin.fr>

On Fri, Jul 19, 2013 at 3:29 PM, Stéphanie Vilayphiou wrote:
>
> So I tried to run first-setup.sh in /opt/context as root.
> First of all, I have troubles with rsync connections through first-setup.sh.
>
>
> """
> rsync: failed to connect to contextgarden.net: Connection timed out (110)
> rsync error: error in socket IO (code 10) at clientserver.c(122)
> [Receiver=3.0.7]

Does anyone else have that problem? Does root user get proper DNS settings?

I can check the server logs, but it's more likely that there are some
weird server settings on your side if it works for regular user and
only fails when you run sudo. Another (not likely, but possible)
option is that you actually run a different binary when you use sudo.

> So I copy/pasted the files from the single-user install in /opt/context/.
> Then Context runs only if I source it with: "source
> /opt/context/tex/setuptex" but putting it in my $PATH doesn't work and it
> disappears from my path when I come back to su.
> """
> root@erba-web1:~# echo $PATH
>     /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> root@erba-web1:~# PATH=$PATH:/opt/context/tex/texmf-linux-64/bin
> root@erba-web1:~# echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/context/tex/texmf-linux-64/bin
> root@erba-web1:~# exit
> $ sudo su
> root@erba-web1:/home/admin_esad# echo $PATH
>     /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> """

This is expected.

> (actually this $PATH thing doesn't work either on my local machine, I have
> to source it every time I want to use it...)
>
> Any idea?

What distribution is running on the server? See for example

http://askubuntu.com/questions/128413/setting-the-path-so-it-applies-to-all-users-including-root-sudo

You need to edit some configuration file that applies path to all
users. I would suggest hardcoding the path in that system setting
rather than sourcing setuptex. Please also be careful about setting
TEXMFCACHE path. Personally I would create a texmf.cnf file somewhere
next to texmf-foo trees setting that variable to something that won't
clash between users (each user needs his own TEXMFCACHE path).

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2013-07-19 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 13:29 Stéphanie Vilayphiou
2013-07-19 13:45 ` Mojca Miklavec [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALBOmsYmkiVuDONnE1n6Kh+C4Pqb6JuEGV_8wQm=tU1oM13Zag@mail.gmail.com' \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).