It seems pool is back again. Looks not steady.
Set up both a pool and a solo miner, give the pool one a higher priority - if the pool works, that should use all the processing power, if the pool is down that miner uses almost no processing power and it goes to the solo miner instead.
( Or you could just solo mine, if you've got a fair amount of processing power to begin with. )
You must have come from some other coin-land, let me remind you, solo is almost impossible with slimcoin wallet, rpcthreads is not supported so you are left with 1. running a full wallet on every node you mine off or 2. err i'm not going to bother describing my set up, it works but i have to keep an eye on all wallets 24/7. Simple restart script wont work as i have to rebuild blockchain databases every couple of hours.
EDIT :
This is what i have to deal with every hour :
*** glibc detected *** slimcoind: double free or corruption (fasttop): 0x00007f26cc000ac0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x76166)[0x7f2705e84166]
/usr/lib64/libstdc++.so.6(_ZNSs6assignERKSs+0x85)[0x7f27066d9565]
slimcoind(_Z8ReadHTTPRSiRSt3mapISsSsSt4lessISsESaISt4pairIKSsSsEEERSs+0xe5)[0x50ac45]
/usr/local/lib/libboost_thread.so.1.55.0(+0xcaa3)[0x7f2707b64aa3]
/lib64/libpthread.so.0(+0x79d1)[0x7f27069499d1]
/lib64/libc.so.6(clone+0x6d)[0x7f2705ef6b6d]
======= Memory map: ========
00400000-00636000 r-xp 00000000 08:03 2623376 /usr/local/bin/slimcoind
00835000-00837000 r--p 00235000 08:03 2623376 /usr/local/bin/slimcoind
00837000-00838000 rw-p 00237000 08:03 2623376 /usr/local/bin/slimcoind
00838000-0083b000 rw-p 00000000 00:00 0
00a98000-00ad1000 rw-p 00000000 00:00 0
00ad1000-00ad2000 rw-p 00000000 00:00 0
00ad2000-00ada000 rw-p 00000000 00:00 0
00ada000-00c36000 rw-p 00000000 00:00 0
00c36000-00c37000 rw-p 00000000 00:00 0
00c37000-00ca1000 rw-p 00000000 00:00 0
Is that crash when you point all slimminer instances to a single wallet? Or each node has it's own wallet?
