I havent been keeping up. What exactly has he said that warrants an entire attack thread dedicated to him ?

... I'm new here, & this is among my first impressions of the BitShares community:

Quote from: FuLl on September 14, 2014, 01:57:28 am

Quote from: tonyk on September 14, 2014, 01:53:38 am

Why did you change you handle?
...

What are you referring to? I registered as FuLl originally. Am I misunderstanding what you mean?

Sorry, Chicken-brain-nes must be more widely spread, than my models suggested...

...I will update the models , if those findings are confirmed...

...In the meanwhile, are you positive you do not have wings and a real good eye site?

Apparently he decided I was someone he doesn't care for, without doing any due diligence to determine if I deserve this kind of treatment (as if _anyone_ does).

Seriously people, if I didn't believe in the project, I would've turned around & walked away never to return right then.

EDIT:
To clarify, I don't believe he should be excommunicated, as apparently he has redeeming value. I think a thread like this to bring the matter to his attention, is indeed appropriate.

I just got my seed node up & running properly:

54.165.9.208

Happy to contribute! :-)

Finally got it working! :-)

Had to change from Debian to Ubuntu for the startup script to work.

54.165.9.208 for anyone who wants to use it.

Screen -dm starts the client when I run the script manually, but it won't start at boot, even after I do:
$sudo update-rc.d btsx defaults
But it won't start at boot.

What are other people's init scripts looking like that work?

Are there 'Required Start' parameters I need to add?

This is my script:

#!/bin/sh
# Starts bitsharesx
#

### BEGIN INIT INFO
# Provides:             bitshares_client
# Required-Start:       $syslog
# Required-Stop:
# Should-Start:
# Default-Start:        2 3 4 5
# Default-Stop:         0 1 6
# Short-Description:    bitshares_client
### END INIT INFO

case "$1" in
start)
        echo ""
        echo "Starting BitSharesX"
        echo ""
sleep 5
        screen -dm bitshares_client --daemon
sleep 10
        $0 view

;;

view)
        ps -e | grep bitshares_client
;;


*)
        echo "Usage: $0 {start}"
        exit 1
esac


I don't know if stop is an actual command though, it was an example cause that's how other clients work, like bitcoin and its many clones.

Check the possible options with --help.

I'm using the stop/exit commands as per the documentation here:
https://github.com/BitShares/bitshares_toolkit/wiki/Bitshares-commands:-General

--help doesn't mention how to exit it.

BitsharesX is the GUI, you need to start "bitshares_client --daemon".

Thanks, that did it, but now I have a new problem.

I start it from a script in etc/init.d, & when I start it, it displays the following output, but doesn't release my console back to a bash prompt.

Starting BitSharesX

Loading blockchain from: /root/.BitSharesX/chain
Loading config from file: /root/.BitSharesX/config.json
Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Successfully re-indexed 0 blocks in 0 seconds.
Starting JSON RPC server on port 43021 (localhost only)
Starting HTTP JSON RPC server on port 38631 (localhost only)
Running in daemon mode, ignoring console

Is there a way to get my prompt back after I start it?

Plus, once I <Ctrl-C> to exit that, if I do:
$bitshares_client exitI get the following output, with a prompt I have to type 'quit' at to exit completely.
$ bitshares_client exit
Loading blockchain from: /home/admin/.BitSharesX/chain
Loading config from file: /home/admin/.BitSharesX/config.json
Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Successfully re-indexed 0 blocks in 0 seconds.
Starting JSON RPC server on port 56544 (localhost only)
Starting HTTP JSON RPC server on port 46261 (localhost only)
Attempting to map P2P port 1776 with UPNP...
Listening for P2P connections on port 1776
Adding peer 80.240.133.79:1776 to peer database
Adding peer 104.131.35.149:1776 to peer database
Adding peer 178.62.50.61:1776 to peer database
Adding peer 178.62.157.161:1776 to peer database
Adding peer 178.62.50.61:1779 to peer database
Adding peer 180.153.142.120:1777 to peer database
Adding peer 188.226.195.137:60696 to peer database
Adding peer 5.101.106.138:1777 to peer database
Adding peer 80.240.133.79:1778 to peer database
Adding peer 95.85.33.16:8764 to peer database
Adding peer 61.129.33.213:1776 to peer database
Adding peer 84.238.140.192:42577 to peer database
Adding peer 54.77.51.177:1776 to peer database
Adding peer 5.101.106.138:1778 to peer database
Adding peer 5.101.106.138:1776 to peer database
Adding peer 178.62.50.61:1777 to peer database
Adding peer 80.240.133.79:1777 to peer database
Adding peer 54.79.27.224:1776 to peer database
Adding peer 178.62.50.61:1778 to peer database
Adding peer 89.187.144.203:8764 to peer database
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 550807 blocks left to fetch
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 9 active connections to the p2p network
--- there are now 10 active connections to the p2p network
--- there are now 11 active connections to the p2p network
--- there are now 12 active connections to the p2p network
--- there are now 13 active connections to the p2p network
--- there are now 14 active connections to the p2p network
--- there are now 15 active connections to the p2p network
(wallet closed) >>>
How do I exit fully & get a command prompt back?

I think there's a typo in your preferences:

Code: [Select]

Pin: release a=sid
a= means the Archive or Suite and should be "unstable"
if you want to say "sid" you should do

Code: [Select]

Pin: release n=sid
that's why "-t unstable" didn't work for you

I also think it's a bad idea to explicitly name all dependencies and their dependencies since versions  might change, and you may not get them all

try:

Code: [Select]

Package: *
Pin: release a=unstable
Pin-Priority: 50

just that, and then

Code: [Select]

apt-get -t unstable install bitsharesx
that should install, in order:
1) bitsharesx
2) bitsharesx-cli
3) dependencies of bitsharesx* found in Stable
4) dependencies of bitsharesx* found in unstable that are not present in Stable

Debian libraries are designed to be co-installable, so there shouldn't be any conflicts either.

let me know if this works! I'll add instructions to the PPA if so. I'll test it too.

Changing that typo didn't have any effect. I still get the same error:
$ sudo aptitude install -t unstable bitsharesx
The following NEW packages will be installed:
  bitsharesx bitsharesx-cli{a} libdb5.3{a} libdb5.3++{a} libdrm-intel1{a}
  libdrm-nouveau1a{a} libdrm-radeon1{a} libdrm2{a} libegl1-mesa{a}
  libegl1-mesa-drivers{a} libffi5{a} libgbm1{a} libgl1-mesa-dri{a}
  libgl1-mesa-glx{a} libglapi-mesa{a} libgstreamer-plugins-base0.10-0{a}
  libgstreamer0.10-0{a} libicu52{a} libopenvg1-mesa{a} liborc-0.4-0{a}
  libpciaccess0{a} libqt5core5a{a} libqt5dbus5{a} libqt5gui5{ab} libqt5network5{a}
  libqt5opengl5{a} libqt5printsupport5{a} libqt5qml5{a} libqt5quick5{a}
  libqt5sql5{a} libqt5sql5-sqlite{a} libqt5webkit5{a} libqt5widgets5{a}
  libwayland0{a} libwebp5{a} libx11-xcb1{a} libxcb-dri2-0{a} libxcb-glx0{a}
  libxcb-render0{a} libxcb-shape0{a} libxcb-xfixes0{a} libxcomposite1{a}
  libxdamage1{a} libxfixes3{a} libxslt1.1{a} libxxf86vm1{a} qttranslations5-l10n{a}
0 packages upgraded, 47 newly installed, 0 to remove and 0 not upgraded.
Need to get 41.9 MB/83.8 MB of archives. After unpacking 302 MB will be used.
The following packages have unmet dependencies:
 libqt5gui5 : Depends: libgbm1 (>= 8.1~0) but 8.0.5-4+deb7u2 is to be installed.
              Depends: libgtk2.0-0 (>= 2.24.0) but it is not going to be installed.
              Depends: libharfbuzz0b (>= 0.9.11) but it is not going to be installed.
              Depends: libmtdev1 (>= 1.0.8) but it is not going to be installed.
              Depends: libpango-1.0-0 (>= 1.14.0) but it is not going to be installed.
              Depends: libudev1 (>= 183) but it is not going to be installed.
              Depends: libxcb-icccm4 (>= 0.4.1) but it is not going to be installed.
              Depends: libxcb-image0 (>= 0.3.9) but it is not going to be installed.
              Depends: libxcb-keysyms1 (>= 0.3.9) but it is not going to be installed.
              Depends: libxcb-randr0 (>= 1.3) but it is not going to be installed.
              Depends: libxcb-render-util0 but it is not going to be installed.
              Depends: libxcb-shm0 but it is not going to be installed.
              Depends: libxcb-sync1 but it is not going to be installed.
              Depends: libxcb-xkb1 but it is not going to be installed.
              Depends: libxi6 (>= 2:1.2.99.4) but it is not going to be installed.
              Depends: libxkbcommon-x11-0 (>= 0.4.0) but it is not going to be installed.
              Depends: libxkbcommon0 (>= 0.4.1) but it is not going to be installed.
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     bitsharesx [Not Installed]
2)     libqt5gui5 [Not Installed]
3)     libqt5opengl5 [Not Installed]
4)     libqt5printsupport5 [Not Installed]
5)     libqt5quick5 [Not Installed]
6)     libqt5webkit5 [Not Installed]
7)     libqt5widgets5 [Not Installed]



Accept this solution? [Y/n/q/?]
Right now I have an interim workaround in that I've created a script which copies all my apt-pinning .pref files to a staging directory, runs aptitude update & aptitude install -y bitsharesx, then copies the .pref files back to /etc/apt/preferences.d/, so that future aptitude upgrade operations won't break the system. It's not perfect, but it works for now. I'll set up cron once I get the BitSharesX command to work correctly & the seed node is up & running. Thanks nevertheless.