Ok timing must have been bad SpyPower The link has been working both times I have tested it. Wineserver and Winedevice to parts of wine are on different PID's. Nicing wine application.exe higher than those equals stuff up at first it appears to give performance gains but sooner or latter you will have lockups. Then nicing wine higher than X11 server also leads to issues. Basically it going to come back and bite. The command to switch users back is su -c "command" <username> problem is its a stacked up mess. With lots of sections running as root. Issue here with su -c commands is that the high access code is still running. This is a breach of good secuirty. Please do a "ps -U root -u root u". You will notice there is very little on the system running as root. That is the way the system should be kept. Goal should be to reduce the numbers running as root. Not creating scripts that add to that list. You are far better off from a secuirty point of view to get applications PID's and Wineserver and winedevices PID's and do it that way. Reason clean does not leave privileged programs running. PID renice alteration as root is not running wine as root. Wine gets to remian as a normal user where it should be. Basically you are trying to do something single line that should not be done single line. One line to start the application other items to find and alter the nice on the PID after the application is running. Wine running as root has a history of killing complete Linux systems. Few viruses cannot tell the difference between a Linux ELF and a Windows ELF running under wine so infected everything. Problem is since the code is not designed for Linux any ELF it infects no longer works. Root allows executable to be altered. Basically audit your commands if its going to lead to wine running as root don't do it.
