is this right or have i missconfig my p2pool or bitcoind
2015-12-18 19:53:19.721694 Local: 409GH/s in last 10.0 minutes Local dead on arrival: ~3.4% (2-6%) Expected time to share: 3.2 hours
2015-12-18 19:53:19.721759 Shares: 0 (0 orphan, 0 dead) Stale rate:
Efficiency:
Current payout: (0.0100)=0.0100 BTC
2015-12-18 19:53:19.721812 Pool: 1131TH/s Stale rate: 25.0% Expected time to block: 3.5 days
p2pool start up:
-a 1DSPW6L2tvCKVDvT9Qiq2RGs7rscwYSfxF --bitcoind-address 192.168.1.1 --logfile /var/log/p2pool --net bitcoin --give-author 0 --no-bugreport -f 0 --max-conns 8 --external-ip externalIP:9330
((if you specifiy "-a 1DSPW6L2tvCKVDvT9Qiq2RGs7rscwYSfxF" like i have done does that mean all people that mine to p2pool goes to me or is it the btc you have set on the miner it self)) reread it. nvm on that..
but if i use -f FEE_PERCENTAGE, --fee FEE_PERCENTAGE where does the fee go to. how do i set it so it goes to my wallet
bitcoind:
DAEMON_ARGS="-daemon -listen -conf=/home/bitcoind/.bitcoin/bitcoin.conf"
# bitcoin.conf configuration file. Lines beginning with # are comments.
# Network-related settings:
# Run on the test network instead of the real bitcoin network.
#testnet=0
# Connect via a socks4 proxy
#proxy=127.0.0.1:9050
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333
addnode=104.238.174.252:9332
addnode=80.74.153.50:9332
# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=0
# Maximum number of inbound+outbound connections.
maxconnections=100
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
server=1 #tells Bitcoin-QT to accept JSON-RPC commands.
server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=bitcoind
rpcpassword=bitcoinandkarlsson050607
# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*/24
rpcallowip=192.168.1.0/24
rpcallowip=213.66.108.0/24
# Listen for RPC connections on this TCP port:
rpcport=8332
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect=127.0.0.1
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1
# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem
# Miscellaneous options
# Set gen=1 to attempt to generate bitcoins
#gen=0
# Use SSE instructions to try to generate bitcoins faster.
#4way=1
# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
paytxfee=0.0001
# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1
# User interface options
# Start Bitcoin minimized
#min=1
# Minimize to the system tray
#minimizetotray=1
blockmaxsize=1000000
mintxfee=0.00001
minrelaytxfee=0.00001
not too long before it see that ... i think. 
