Author Topic: [API] example access restriction file leads to 11 eof_exception: End Of File  (Read 1607 times)

0 Members and 1 Guest are viewing this topic.

Offline monsterer

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 :)
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline theoretical

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.
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline monsterer

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.
« Last Edit: October 23, 2015, 01:46:26 pm by monsterer »
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
is the file located in the same directory from which you launch the witness node?

Offline monsterer

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?
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads