Sorry all, its been a busy weekend and I haven't been around much (family plans, 4th of July, wife's birthday...)
I'll try to catch up on all the questions:
I don't care what you do with smartcoin locally, but I definitely would not appreciate it if you branched off to add support for installing it anywhere and changed the donation profiles. I literally have hundreds of hours of my time into this. To be up-front with you (and everybody), smartcoin makes me next to nothing - I've received 4 BTC in donations, 0 BTC from the "pledges" that were made, and about 0.019 BTC (about 2 bit cents) per day via autodonate. Be patient, support will come to move it to an arbitrary directory pretty soon actually, as things are stabilizing out quite a bit.
I'll modify the installer to make auto-detection optional. The linux locate command simply is not reliable without running updatedb before hand.
Aside from that, your install is quite unique in that most people mine on completely stripped down machines, dedicated solely to mining. Most people wouldn't even dream of running 5 drives packed full of files on their miners, so understand that features that are made are assuming the case of the normal average user. But I'll definitely try to keep special cases like this in mind in the future, thanks for the report
I can change that, though I commonly see it represented both ways
#pass#, not #path".
Actually, both are valid. The current list of tags includes: <#path#>,<#user#>,<#pass#>,<#server#>,<#port#>,<#device#>
it looks like more pools = more rejections
I don't have that problem here. I run 4 different workers on each GPU, with 3 GPUs. My rejections are almost always under 1%. I have seen other installs over SSH which mimic this behavior, and have no extra rejection problems. Additionally, I see no performance hit running multiple instances eaither. (perhaps it related to an outdated phoenix, what phoenix revision are you running?)
Can we assign also specific miner to device?
I will be adding this feature very very soon (tomorrow most likely), the only thing you will have to watch out for is running 2 different miners on one card (i.e. phoenix and poclbm on the same card), as they could be running different kernels. However, running different instances of phoenix with unique parameters is more the type of thing you would be wanting to do.
I have seen this report a couple of times, and now have the problem figured out. When things appear to lock up in the down state, its most likely that phoenix is reporting "Work queue empty. Miner Idle". This is a long standing phoenix connection bug in older phoenix versions. (If it happens again, look at the miner screen (screen -r miner). You will likely find one or more of the phoenix instances with this error.
I used to get this error all the time in phoenix. I switched to phoenix r100 about 3 weeks ago, and haven't had the problem since.
Anyone having this problem, I highly recommend getting updated versions of phoenix installed (I recommend r100, as I know it works well regarding their connection bug, but I'm sure even more recent updates are fine too)
If phoenix was installed via svn, just run:
svn update -r 100
If you wanted to start fresh with checking out phoenix r100, I would use something like:
svn checkout -r 100 http://svn3.xp-dev.com/svn/phoenix-miner/trunk
also, I have been running the same phatk kernel mod for a while now, with no problems at all.
Also, I ssh'd in and smartcoin is up and running, you accidentally misspelled <#device#> as <#devic#> in your miner launch string