I did try without snap. That's when I was getting an error about being able to set a priority for a separate thread. I don't have that verbatim.
Here's the content of the pharo script: #!/usr/bin/env bash # some magic to find out the real location of this script dealing with symlinks DIR=`readlink "$0"` || DIR="$0"; DIR=`dirname "$DIR"`; cd "$DIR" DIR=`pwd` cd - > /dev/null # disable parameter expansion to forward all arguments unprocessed to the VM set -f # run the VM and pass along all arguments as is "$DIR"/"pharo-vm/pharo" --nodisplay "$@" ------ Mark Guzdial, mj...@umich.edu - Professor of Electrical Engineering and Computer Science, and Engineering Education Research, College of Engineering and Professor of Information, School of Information (courtesy) - Blog: http://computinged.wordpress.com On Thu, May 28, 2020 at 4:08 PM Stéphane Ducasse <stephane.duca...@inria.fr> wrote: > mark > > can you show us the contents of the pharo command because may be it is > wrapping the Pharo command. > did you try without snap (no idea what is it). > Did you the script of sven because they work without snap. > > S > > On 28 May 2020, at 18:23, Mark Guzdial <mj...@umich.edu> wrote: > > Hi everyone, > > New here, encouraged (from Discord) to try my questions here. > > I’m struggling to get AWS to run in an Ubuntu AWS instance. I tried > following the directions here: > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/DeploymentWeb/DeployForProduction.html > but > I was getting some error about threads and configurations that I simply > didn’t understand. Then I tried using Pharo-snap: > https://github.com/akgrant43/pharo-snap > > Pharo-snap made some of the config problems go away, but when I try > starting Pharo on AWS, I get: > > *ubuntu@ip-172-31-16-17*:*~*$ ./pharo Pharo-sea-roa-sound.image > > Usage: [<subcommand>] [--help] [--copyright] [--version] [--list] [ > --no-quit ] > --help print this help message > --copyright print the copyrights > --version print the version for the image and the vm > --list list a description of all active command line handlers > --no-quit keep the image running without activating any other command > line handler > --deploymentPassword if a password needs to be used by the user to > launch the command > --readWriteAccessMode, --readOnlyAccessMode, --writeOnlyAccessMode, > --disabledAccessMode > specify disk access mode, read-write mode as default > <subcommand> a valid subcommand in --list > > > Preference File Modification: > --preferences-file load the preferences from the given <FILE> > --no-default-preferences do not load any preferences from the default > locations > > > Documentation: > A PharoCommandLineHandler handles default command line arguments and > options. > The PharoCommandLineHandler is activated before all other handlers. > It first checks if another handler is available. If so it will activate > the found handler. > > > Clearly, I’m doing something wrong, but don’t know what the next step is, > since there isn’t an explicit error message. > Can someone point a newbie towards the appropriate next steps? > > Thanks! > - Mark > > > -------------------------------------------- > Stéphane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, Bât.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >
