GNU/Linux S5R3 App 4.49 available for Beta test

And it shows us your E@H directory is a total mess. :-)
But first your sudo problems. When you (as user perle) run:

$ sudo su -m You should get a real root-shell:

# id -rnu; id -nu
root
root

You will remain root until:

# exit
$ id -rnu; id -nu
waldi
waldi

But first, as root:

# vigr Move the cursor to the line that starts with 'boinc:', type 'A' and add 'perle' at the end of the line after the colon:

boinc:!:NNN:perle Where NNN is a number. Type ESC and ':x'ENTER and then you are a member of group 'boinc'. Continue with:

# cd /var/lib/boinc-client/projects/einstein.phys.uwm.edu
# chmod 0755 einstein*
# chmod 0644 app_info.xml
# cd ../..
# chown -R boinc:boinc .
# find . -type d -print0 | xargs -0 chmod 0755
# find . -type f -print0 | xargs -0 chmod u+rw
# find . -type f -print0 | xargs -0 chmod g+r
# chmod 0440 gui_rpc_auth.cfg
# chmod 0750 .
# exit

To manipulate files in /var/lib/boinc-client/* when necessary:

# sudo su -m
# cd /var/lib/boinc-client
# su boinc
# umask 022

Ownership (user and group) and permissions will not change by accident. To install new beta-applications, you'll still need a root-shell to change user and group ownership to boinc:boinc after downloading and unpacking. And remember to check permissions. :-D

Regards,
Waldi

Have completed a WU (this one). It normally should take me under 28,000 seconds to do even the Peak type work units, but this one took well over 38,000 seconds.

It had stopped at 97% for some time with the status of 'running' but nothing was happening, no cpu time or progress percent done. I suspended and restarted, as it had started another WU I did not see this particular one restart.

It apparently did restart but took a darn long time to finish.

Try this: as user root:

chown -R boinc:boinc /var/lib/boinc-client/projects/einstein.phys.uwm.edu

CU
Bikeman

Bikeman has given you the command to change both owner and group but I thought it might be useful to put in yet another plug for convincing yourself to use man pages.

To change the owner to boinc you obviously discovered the 'chown' (change owner) command. If you had done a 'man chown' you wou would have gotten the following command synopsis right at the top of the page:-

chown [OPTION].... [OWNER][:[GROUP]] FILE....

You interpret that synopsis as follows (please realise that anything inside square brackets is optional):-

• * The command name is chown
  * The command does accept several options
  * options are optional - ie you don't have to supply any if you don't want to
  * The command accepts owner and group names (in several optional formats)
  * You could use 'owner' by itself to change owner without changing group
  * You could use 'owner:' - read the man page to see exactly what that does
  * You could use ':group' - again, read the man page
  * You could even use ':' on its own and once again this is described
  * Finally you need to supply one or more files or directories.
  

Once you understand the basic command syntax, have a look for useful options. They can be short, like -R, or long like --recursive, both of which are allowed. This option is particularly useful because it allows you to change the ownership of zillions of files in one simple command.

There's only one modification to Bikeman's suggested command that I would make. You should use
chown -R boinc:boinc /var/lib/boinc-client
just in case there are any other root owned files lurking anywhere else in the kingdom of boinc :-).

I guess one of the problems with finding information about commands is that you need to know the name of the command in order to read its man page. New users will suffer from not knowing the names of useful commands. You can get around this to some extent by using the 'apropos' command (check out its man page) with a likely keyword such as 'owner' as shown in the next example

apropos owner which will return you a list of command names that are useful for file ownership purposes. You could use the 'group' keyword instead of 'owner' and get an even more extensive list.

Some people complain that man pages are too hard to read and understand. To some extent this is true, particularly when you are first starting. It is an effort to read the detail very carefully and quite often you can miss very important stuff by skipping through too quickly. The more you read the easier it gets :-).

Good Luck!!