BitShares Forum

Main => Technical Support => Topic started by: monsterer on October 23, 2015, 01:25:35 pm

Title: [API] example access restriction file leads to 11 eof_exception: End Of File
Post by: monsterer on October 23, 2015, 01:25:35 pm
I'm trying to set up access to the history and broadcast APIs, which I understand require the api-access field to be set inside config.json for the witness.

However, the example given here: http://docs.bitshares.eu/api/access.html results in an exception :

Code: [Select]
11 eof_exception: End Of File
Any advice?
Title: Re: [API] example access restriction file leads to 11 eof_exception: End Of File
Post by: xeroc on October 23, 2015, 01:39:21 pm
is the file located in the same directory from which you launch the witness node?
Title: Re: [API] example access restriction file leads to 11 eof_exception: End Of File
Post by: monsterer on October 23, 2015, 01:44:01 pm
is the file located in the same directory from which you launch the witness node?

No, its in the witness_data_dir, but I specify the path

edit: figured it out - none of the cryptonomex tools appear to understand the ~ directive in path names, you have to use the fully qualified form.
Title: Re: [API] example access restriction file leads to 11 eof_exception: End Of File
Post by: theoretical on October 23, 2015, 03:29:48 pm
edit: figured it out - none of the cryptonomex tools appear to understand the ~ directive in path names, you have to use the fully qualified form.

Traditionally ~ interpolation is a function of the shell.  I'm pretty sure lots of other Linux programs don't expand ~ in their configuration files.
Title: Re: [API] example access restriction file leads to 11 eof_exception: End Of File
Post by: monsterer on October 23, 2015, 03:39:55 pm
edit: figured it out - none of the cryptonomex tools appear to understand the ~ directive in path names, you have to use the fully qualified form.

Traditionally ~ interpolation is a function of the shell.  I'm pretty sure lots of other Linux programs don't expand ~ in their configuration files.

No problem - it just caught me out is all :)