On Nov 19, 5:54 pm, Avery F wrote:
> Alright. Sorry for the above post, when I tried that previously it
> failed due to the port error. Yet when run under root, it seemed to
> work. Why does the argument seem to want an actual network interface
> ID, yet actually wants an IP?
If I'm not mistak
Alright. Sorry for the above post, when I tried that previously it
failed due to the port error. Yet when run under root, it seemed to
work. Why does the argument seem to want an actual network interface
ID, yet actually wants an IP?
On Nov 19, 8:35 pm, William Stein wrote:
> On Saturday, Nov
Can someone else with access to a Linux box confirm this? Try setting
up a new, unprivileged user and running sage as that user. Then, try
and run the notebook and bind to a port, eg notebook(interface=eth0,
port=8000)
Obviously, change settings to fit your needs.
--
To post to this group, send
With respect, no. The interface argument works as expected when run
as root. The problem is sage throwing errors when not given root and
told to bind to a port that does not require root access. Binding to
the port works just fine from other applications not running as root.
At this point, I'm p
On Wed, Nov 16, 2011 at 5:27 PM, Avery F
wrote:
> So I was trying to set up sage on a server I run, but no matter what port I
> ask the notebook to bind to, I get an error as displayed here:
>http://pastebin.com/H9NSQJxc.
I think the "interface" argument needs to be an IP address, not the
"eth0",
Running as root does seem to work, at least no error is produced.
However, this cannot be a long-term solution. Binding to port 25000
shouldn't require root from the system, should it?
On Nov 16, 11:50 pm, William Stein wrote:
> On Wed, Nov 16, 2011 at 5:27 PM, Avery F wrote:
> > So I was tryin
