Yes I do, and I read through it first, but it was of no help (kind of like your comment (except minus the psychological neediness)).

For closure, and anyone following this, my account was silently blocked from payouts (and only the payout functionality was affected)
due to an ip address from which I logged in at one point being flagged for suspicious behavior.

dhcp, tor, public nats, etc. make the 'ip used in an attack' a blunt tool, and that along with the silent/invisible
block was the issue in this case.

True to his word, the coinotron rep who responded tracked this down and fixed it...and did it quickly as well, so kudos, thanks, and trust++. 

He also acknowledged the 'bluntness' and pointed out that they implemented 2-factor GA to help mitigate this.

Hello,

I've had a coinotron account for a while, but used it only sporadically.
I recently turned up 7,000k worth of LTC mining, and generated a few coins but they never
get paid out, despite the 'paid every 60 minutes' and meeting the payment threshold.
I've tried changing payment amount and address to hopefully trigger it, but no
luck, they just sit there.

Can anybody tell me what I'm missing, or what's up?

thanks

(I emailed coinotron a couple of days ago, but no reply)

I started using this about 2 weeks ago. It has been flawless so far and the interface is nice and clean.
Not big enough to be a target yet, and my stale rate is virtually zero... my 2cents and another data point

I run a 7850 from a 250w supply using the 4pin dvd, and a second 7850 from a 305w supply also using 4pin - pcie.
They have been running continuously for a couple of months with no cable-overheat issues... no issues
of any kind really. 365kh each

The 250 supply is right on the edge.

thanks for that. I expect I'm being obtuse, but can you
tell me why this does not work?


rc.local:
/usr/bin/screen -dmS cgm /x/y/z/go


/x/y/z/go:
#!/bin/sh
sleep 30
export DISPLAY=:0
cd /x/y/z
/x/y/z/cgminer -o http ...    > /tmp/looky 2>&1


/tmp/looky:
 [2013-05-14 18:20:05] Started cgminer 3.1.0
 [2013-05-14 18:20:05] Started cgminer 3.1.0
No protocol specified
 [2013-05-14 18:20:05] clDevicesNum returned error, no GPUs usable
 [2013-05-14 18:20:05] clDevicesNum returned error, no GPUs usable
 [2013-05-1418:20:05] All devices disabled, cannot mine!
 [2013-05-14 18:20:05] All devices disabled, cannot mine!
(with escape sequences edited out)


clGetDeviceIDs() still fails


thanks for any insight

I have a tiny script to launch cgminer which works fine.


go:

  #!/bin/sh
  set -x
  cd /x/y/z
  /x/y/z/cgminer ...


UNLESS I launch it from rc.local:

  nohup /x/y/z/go > /dev/null 2>&1 &



in this case clGetDeviceIDs() fails, which causes clDevicesNum() in ocl.c to fail, which aborts everything.


 [2013-05-13 19:56:01] Started cgminer 3.1.0
 [2013-05-13 19:56:01] Started cgminer 3.1.0 No protocol specified
 [2013-05-13 19:56:02] CL Platform 0 vendor: Advanced Micro Devices, Inc.
 [2013-05-13 19:56:02] CL Platform 0 name: AMD Accelerated Parallel Processing
 [2013-05-13 19:56:02] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2)
 [2013-05-13 19:56:02] Error -1: Getting Device IDs (num)
 [2013-05-13 19:56:02] clDevicesNum returned error, no GPUs usable
 [2013-05-13 19:56:02] CL Platform 0 vendor: Advanced Micro Devices, Inc.
 [2013-05-13 19:56:02] CL Platform 0 name: AMD Accelerated Parallel Processing
 [2013-05-13 19:56:02] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2)
 [2013-05-13 19:56:02] Error -1: Getting Device IDs (num)
 [2013-05-13 19:56:02] clDevicesNum returned error, no GPUs usable
 [2013-05-13 19:56:02] All devices disabled, cannot mine!
 [2013-05-13 19:56:02] All devices disabled, cannot mine!

(I edited out the ASCII escape sequences used for screen display)




rc.local is launched as the final thing coming up into run level 3 -  S99rc.local  in rc3.d   starts it up.


If I run rc.local directly, it also works, if I reboot it does not, and fails as above.


What's different between the two cases? I captured the environment for the working case:

env > xxx

then sourced it from go:

  #!/bin/sh
  set -x
  cd /x/y/z
  . /x/y/z/xxx
  /x/y/z/cgminer ...

but that did not help either.


One side note is the "No protocol specified" error in the does-not-work case, which I don't think comes from
cgminer source.


I thought I'd ask before digging deeper.

thanks

Did you ever find an answer? I am facing the same problem.

rc.local (usually) runs as the last thing coming up into run level 3... via S99rc.local  in /etc/rc3.d,

so it does not seem like it should be the driver... I just started looking into environment issues,
but saw this and thought I'd ask if you solved it yet.

thanks

For what it is worth:

from this page:  https://bitcointalk.org/index.php?topic=201027.0
this link: https://mega.co.nz/#!pUMBkbbY!cMJYcFqPCMr1idZBr30VsFw0tLY7y63J0N4RVNYMUBc


$ sum *.exe
03133   350 minerd_scrypt_jane_x64_avx.exe
45517   351 minerd_scrypt_jane_x64_ssse3.exe

$ md5sum *.exe
9e8878a529978dcbc943e93ccb65aa33 *minerd_scrypt_jane_x64_avx.exe
1b5a6331149a462e15498909c1462754 *minerd_scrypt_jane_x64_ssse3.exe


run as:

./minerd_scrypt_jane_x64_avx.exe -a scrypt-jane -o http://mineyac2.dontmine.me:8080 -O myuser



made only these connections over the course of 8 hours.
  TCP    192.168.1.27:57598     54.215.7.83:8080       ESTABLISHED
  TCP    192.168.1.27:57599     54.215.7.83:8080       ESTABLISHED

stat(2) appears to not show any of bitcoin, litecoin, terracoin wallets touched
(as in stat'ing continuously from another process in case of touch'ing back)


Shrill claims from either side are pretty useless.

Compiling from source increases the comfort factor, but it is no guarantee unless you read and
understand all the code first. To do that you have to be both capable and (a priori) interested enough.

It's not really possible to detect in any systematic way.  Suppose I have:
unsigned char obf[BUFSIZ];

then memcpy(obf, pointer-to-some-known-place, sizeof(obf));, where the 'known place'
has the ascii values I need. then a bit of pointer arithmetic can construct the file name/process name/whatever
I am looking for in a manner which would not show up via grep or strings() on the binary.

So, if I wanted to open a wallet.dat file in source it would be pretty easy to hide it from all but other
knowledgeable and interested developers.

A google search for 'obfuscated C Code testing apps' isn't going to help out.

Compiling from source is not an absolute guarantee of safety... unless you read and understand all the code, but how many people can/will do that?  It is not too difficult to obfuscate at the source code level (look at the obfuscated C contest each year).

Bad binary behavior starts to get noticed quickly when people start losing something. Until then, it is unlikely the time would be spent to uncover 'issues'.

I can't withdraw my coins from notroll.in

There is a fairly lengthy thread on this over where-I-can't-post... basically
a lot of angry people and an occasional haughty reply from the perp

stay away/be careful

wie gehts

What difference, if any, do you think it would make to psychological uptake
if  some portion of cpu cycles were used for one or more of the several social
distributed computing projects. 

I am referring to NOAA atmospheric research, SETI, cancer research, etc... standing projects
which are happy to have your spare CPU cycles to help with their particular number crunching
needs.


Work done for society and future. Would it help anchor a currency in terms of perceived value?