Changes between Version 1 and Version 2 of CoreClient


Ignore:
Timestamp:
May 3, 2007, 12:44:02 PM (17 years ago)
Author:
KSMarksPsych
Comment:

Change .php links to Wiki links

Legend:

Unmodified
Added
Removed
Modified
  • CoreClient

    v1 v2  
    2626The core client is controlled by a number of other [UnixClient command-line options, configuration files, and environment variables].
    2727
    28 You may want to [http://boinc.berkeley.edu/auto_start.php automatically start the core client] at boot time.
     28You may want to [AutoStart automatically start the core client] at boot time.
    2929
    30 To control a running BOINC client, use the [http://boinc.berkeley.edu/boinc_cmd.php BOINC command tool].
     30To control a running BOINC client, use the [BoincCmd BOINC command tool].
    3131
    32 Several [http://boinc.berkeley.edu/mac_admin_tools.php tools] for Macintosh system administrators are available to:
     32Several [MacAdminTools tools] for Macintosh system administrators are available to:
    3333
    3434    * automatically start BOINC as a daemon or system service at boot time
     
    5454If you must mix the stand-alone core client and the BOINC Manager on the same Mac OS X system, be careful of the following:
    5555
    56     * The BOINC Manager installer sets the set_user_id (S_ISUID) and set_group_id (S_ISGID) permission bits for the BOINC Manager and its embedded core client executable files. This causes BOINC to always run with the effective user ID set to the installing user. This may cause permission problems if the stand-alone core client tries to access the same data as a different user. See [http://boinc.berkeley.edu/sandbox_user.php The Secure BOINC Client] for more information.
     56    * The BOINC Manager installer sets the set_user_id (S_ISUID) and set_group_id (S_ISGID) permission bits for the BOINC Manager and its embedded core client executable files. This causes BOINC to always run with the effective user ID set to the installing user. This may cause permission problems if the stand-alone core client tries to access the same data as a different user. See [SandboxUser The Secure BOINC Client] for more information.
    5757    * By default, the stand-alone core client expects the data to be in the same directory containing the executable. But the BOINC Manager sets the current directory to "/Library/Application Support/BOINC Data/" before launching the embedded core client.
    5858
    59 If you want BOINC to operate on a separate set of data for each user on a Mac OS X system, then the stand-alone core client may be appropriate. But to avoid permission problems, make sure that users who have their own core client don't run the BOINC Manager, unless you have set permissions up properly with the special [http://boinc.berkeley.edu/mac_admin_tools.php administrator tools].
     59If you want BOINC to operate on a separate set of data for each user on a Mac OS X system, then the stand-alone core client may be appropriate. But to avoid permission problems, make sure that users who have their own core client don't run the BOINC Manager, unless you have set permissions up properly with the special [MacAdminTools administrator tools].