OS X → macOS (#2986)
This commit is contained in:
Antoine Cœur
GitHub
parent
026174ae51
commit
42713c6716
|
|
@ -17,7 +17,7 @@ If you are having trouble with Transmission then the things you should do in ord
|
|||
* State the version of Transmission you are using (e.g. Linux/GTK+ 1.80).
|
||||
If you are using a GUI version of Transmission, you can find its version in the `About` dialog in the Help menu.
|
||||
**Do not** say _the latest version_ it's ambiguous.
|
||||
* State what operating system and version (e.g. Mac OS X 10.5.8, Ubuntu 8.04, ...)
|
||||
* State what operating system and version (e.g. macOS 12.3.1, Ubuntu 22.04, ...)
|
||||
* Describe the symptoms in a short yet precise manner.
|
||||
* If the problem is reproducible and you explain how to reproduce it, then it stands a high chance of being addressed.
|
||||
If the problem is intermittent then we still want to know, but if you can not tell us how to reproduce it we cannot easily work on it.
|
||||
|
|
@ -47,7 +47,7 @@ If you are experiencing slow speeds and you have been through the documentation,
|
|||
If you have problems on the Mac version then please do these extra steps:
|
||||
* Make sure your system is updated to the latest version of your operating system. Note as of version 1.60, Transmission requires Mac OS X 10.5 or later.
|
||||
* If you are running a nightly build, set the language to English. The localization will sometimes crash the nightly builds until they are updated (right before an official release).
|
||||
* OS X collects two pieces of crash information that can help us fix the crash:
|
||||
* macOS collects two pieces of crash information that can help us fix the crash:
|
||||
1. In Console.app, look under LOG FILES > ~/Library/Logs/ > CrashReporter > for Transmission. If you find one, include it in your forum post.
|
||||
2. In Console.app, select LOG DATABASE QUERIES > Console Messages, and search for Transmission. If you find a message that mentions an assertion failure, include it in your forum post.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,10 @@
|
|||
## Getting the Source ##
|
||||
The source code for both official and nightly releases can be found on our [download page](https://transmissionbt.com/download/).
|
||||
|
||||
## On Mac OS X ##
|
||||
## On macOS ##
|
||||
Transmission has an Xcode project file (Transmission.xcodeproj) for building in Xcode. Make sure you have this software:
|
||||
* OS X 10.10 or newer
|
||||
* OS X 10.10 SDK
|
||||
* Xcode 4.4 or newer
|
||||
* macOS 10.14.4 or newer
|
||||
* Xcode 11.3.1 or newer
|
||||
|
||||
Building the project on Mac requires the source to be retrieved from GitHub. Pre-packaged source code will not compile.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
## Locations
|
||||
|
||||
### Mac OS X Defaults
|
||||
### macOS Defaults
|
||||
<table>
|
||||
<tr><th>What</th><th>Where</th></tr>
|
||||
<tr><td>Per-torrent settings</td><td><tt>$HOME/Library/Application Support/Transmission</tt></td></tr>
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ Here is a sample of the three basic types: respectively Boolean, Number and Stri
|
|||
* **lpd-enabled:** Boolean (default = false) Enable [Local Peer Discovery (LPD)](https://en.wikipedia.org/wiki/Local_Peer_Discovery).
|
||||
* **message-level:** Number (0 = None, 1 = Error, 2 = Info, 3 = Debug, default = 2) Set verbosity of transmission messages.
|
||||
* **pex-enabled:** Boolean (default = true) Enable [https://en.wikipedia.org/wiki/Peer_exchange Peer Exchange (PEX)].
|
||||
* **prefetch-enabled:** Boolean (default = true). When enabled, Transmission will hint to the OS which piece data it's about to read from disk in order to satisfy requests from peers. On Linux, this is done by passing `POSIX_FADV_WILLNEED` to [posix_fadvise()](https://www.kernel.org/doc/man-pages/online/pages/man2/posix_fadvise.2.html). On OS X, this is done by passing `F_RDADVISE` to [fcntl()](https://developer.apple.com/library/IOS/#documentation/System/Conceptual/ManPages_iPhoneOS/man2/fcntl.2.html). This defaults to false if configured with --enable-lightweight.
|
||||
* **prefetch-enabled:** Boolean (default = true). When enabled, Transmission will hint to the OS which piece data it's about to read from disk in order to satisfy requests from peers. On Linux, this is done by passing `POSIX_FADV_WILLNEED` to [posix_fadvise()](https://www.kernel.org/doc/man-pages/online/pages/man2/posix_fadvise.2.html). On macOS, this is done by passing `F_RDADVISE` to [fcntl()](https://developer.apple.com/library/archive/documentation/System/Conceptual/ManPages_iPhoneOS/man2/fcntl.2.html). This defaults to false if configured with --enable-lightweight.
|
||||
* **scrape-paused-torrents-enabled:** Boolean (default = true)
|
||||
* **script-torrent-added-enabled:** Boolean (default = false) Run a script when a torrent is added to Transmission. Environmental variables are passed in as detailed on the [Scripts](./Scripts.md) page
|
||||
* **script-torrent-added-filename:** String (default = "") Path to script.
|
||||
|
|
@ -172,9 +172,9 @@ Only keys that differ from above are listed here. These options have been replac
|
|||
##### [RPC](rpc-spec.md)
|
||||
* **rpc-access-control-list:** String (Comma-delimited list of IP addresses prefixed with "+" or "-". Wildcards allowed using '\*'. Example: "+127.0.0.\*,-192.168.\*.\*", Default: "+127.0.0.1")
|
||||
|
||||
## Mac OS X
|
||||
## macOS
|
||||
### Overview
|
||||
Mac OS X has a standardized way of saving user preferences files using [XML](https://en.wikipedia.org/wiki/XML) format. These files are called [plist](https://en.wikipedia.org/wiki/Plist) (short for property list) files. Usually there is no need to modify these files directly, since Apple provided a [command-line tool](https://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man1/defaults.1.html) to reliably change settings. You do need to restart Transmission before these have effect.
|
||||
macOS has a standardized way of saving user preferences files using [XML](https://en.wikipedia.org/wiki/XML) format. These files are called [plist](https://en.wikipedia.org/wiki/Plist) (short for property list) files. Usually there is no need to modify these files directly, since Apple provided a [command-line tool](https://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man1/defaults.1.html) to reliably change settings. You do need to restart Transmission before these have effect.
|
||||
|
||||
In short:
|
||||
* To set a key: `defaults write org.m0k.transmission <key> <value>`
|
||||
|
|
|
|||
|
|
@ -6,8 +6,8 @@ For this to be possible, it is required to be accessible from the Internet. Howe
|
|||
## Open your local firewall
|
||||
To allow other peers to communicate with your Transmission instance, you have to forward a port through your firewall.
|
||||
|
||||
### On Mac OS X
|
||||
Upon opening Transmission for the first time, a Mac OS X dialog box should appear asking if you will allow Transmission to receive incoming connections. Click Accept.
|
||||
### On macOS
|
||||
Upon opening Transmission for the first time, a macOS dialog box should appear asking if you will allow Transmission to receive incoming connections. Click Accept.
|
||||
|
||||
If this does not happen, you can add Transmission to Leopard's firewall manually:
|
||||
1. Open System Prefs >> Security >> Firewall. Make sure "Set access for specific services and applications" is selected.
|
||||
|
|
@ -53,7 +53,7 @@ Most routers manufactured since 2001 have either the UPnP or NAT-PMP feature.
|
|||
|
||||
### Forward manually through a router
|
||||
1. Find out what your IP address is.
|
||||
* *On Mac OS X*- Go to System Preferences >> Network, double-clicking on your connection (for instance, Built-in Ethernet), and clicking the TCP/IP tab. The address is probably something like 192.168.1.100, or 10.0.1.2. The IP of your router is here too.
|
||||
* *On macOS*- Go to System Preferences >> Network, double-clicking on your connection (for instance, Built-in Ethernet), and clicking the TCP/IP tab. The address is probably something like 192.168.1.100, or 10.0.1.2. The IP of your router is here too.
|
||||
* *On Unix*- In Ubuntu, right click the Network Manager applet in the menu bar, and select 'Connection Information'. The address is probably something like 192.168.1.2, or 10.0.1.2.
|
||||
* If you don't have Network Manager, open a Terminal and type 'ifconfig'. It will list information for each of your network devices. Find the one you are using, and use the number after 'inet addr:'.
|
||||
* Using the command "ip a" will achieve the same results in a different format.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
## Introduction
|
||||
Thanks to the powerful [RPC](./rpc-spec.md), `transmission-remote` can talk to any client that has the RPC enabled. This means that a script written using `transmission-remote` or [RPC](./rpc-spec.md) can, without rewrite, communicate with all the Transmission clients: Mac, Linux, Windows, and headless.
|
||||
|
||||
Mac OS users may wonder whether there will be AppleScript scripts, the answer is ''no''. Although AppleScript is a nice technology, it's a pain to implement. However, Mac OS X is a Unix after all, so any script you find here will also work on the Mac. Even from within AppleScript, you can run these scripts by typing: `do shell script "path/to/script"`.
|
||||
Mac OS users may wonder whether there will be AppleScript scripts, the answer is ''no''. Although AppleScript is a nice technology, it's a pain to implement. However, macOS is a Unix after all, so any script you find here will also work on the Mac. Even from within AppleScript, you can run these scripts by typing: `do shell script "path/to/script"`.
|
||||
|
||||
## How-To
|
||||
If you are interested at writing scripts for Transmission, have a look at the following pages:
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ The core components and methods of control are shown below:
|
|||
|
||||
|
||||
From the above diagram it can be seen that a Transmission core may be controlled by the following:
|
||||
* _Local_ directly linked GUI (OS X, GTK+)
|
||||
* _Local_ directly linked GUI (macOS, GTK+)
|
||||
* _Local_ or _remote_ Qt GUI
|
||||
* _Local_ or _remote_ command line utility
|
||||
* _Local_ or _remote_ Transmission web application running in a web browser
|
||||
|
|
@ -17,7 +17,7 @@ The multiple methods of controlling Transmission and the various native GUIs ava
|
|||
|
||||
|
||||
The products are:
|
||||
* Transmission desktop - OS X
|
||||
* Transmission desktop - macOS
|
||||
* Transmission desktop - Windows, Linux/Qt
|
||||
* Transmission desktop - Linux/GTK+
|
||||
* Transmission daemon (headless)
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Copyright 2017 Endless Mobile, Inc.
|
|||
<p>
|
||||
Transmission is a BitTorrent client with an easy-to-use frontend on top a
|
||||
cross-platform backend.
|
||||
Native frontends are available for OS X and Windows, as well as command line and
|
||||
Native frontends are available for macOS and Windows, as well as command line and
|
||||
web frontends.
|
||||
</p>
|
||||
<p>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
<head>
|
||||
<META http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
||||
<link media="all" rel="stylesheet" href="../styles/TransBody.css"/>
|
||||
<title>Configuring the Mac OS X Firewall</title>
|
||||
<title>Configuring the macOS Firewall</title>
|
||||
</head>
|
||||
<body>
|
||||
<div id="mainbox">
|
||||
|
|
@ -12,10 +12,10 @@
|
|||
<div id="index"><a class="leftborder" href="../html/index2.html">Index</a></div>
|
||||
</div>
|
||||
<div class="pagetitle">
|
||||
<h1>Configuring the Mac OS X Firewall</h1>
|
||||
<h1>Configuring the macOS Firewall</h1>
|
||||
</div>
|
||||
<br>
|
||||
<p>Upon opening Transmission for the first time, a Mac OS X dialog box should appear asking if you will allow Transmission to receive incoming connections. Click Accept.</p>
|
||||
<p>Upon opening Transmission for the first time, a macOS dialog box should appear asking if you will allow Transmission to receive incoming connections. Click Accept.</p>
|
||||
<p>If this doesn't happen, you can add Transmission to the firewall manually:</p>
|
||||
<div class="taskbox">
|
||||
<ol>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
<div class="pagetitle">
|
||||
<h1>Port Forwarding a Router</h1>
|
||||
</div>
|
||||
<p>If you are using a router, it is probably OK to disable the OS X firewall, as you are already being protected by the router. To disable the firewall, open System Prefs → Security → Firewall. Click Stop.
|
||||
<p>If you are using a router, it is probably OK to disable the macOS firewall, as you are already being protected by the router. To disable the firewall, open System Prefs → Security → Firewall. Click Stop.
|
||||
|
||||
<p>To forward a port in your router manually:
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@
|
|||
</div>
|
||||
|
||||
<p>If you don't have a compatible router, it is simple to forward Transmission's port manually. For instructions <a href="pfrouter.html">click here</a>.</p>
|
||||
<p>If you don't use a router, and your modem is directly connected to your computer, you'll need to open Transmission's port in the Mac OS X firewall. For instructions <a href="pffirewall.html">click here</a>.<br><br> <em>Note:</em> It is highly recommended you enable the Mac OS X firewall if you are not using a router.</p>
|
||||
<p>If you don't use a router, and your modem is directly connected to your computer, you'll need to open Transmission's port in the macOS firewall. For instructions <a href="pffirewall.html">click here</a>.<br><br> <em>Note:</em> It is highly recommended you enable the macOS firewall if you are not using a router.</p>
|
||||
<p>Keep in mind that many DSL modems also function as routers, so port forwarding may still be necessary, even though your computer is directly connected to the modem.</p>
|
||||
|
||||
</body>
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@
|
|||
<p>The second way is to map Transmission's port on all of the devices on your network.
|
||||
Transmission can only automatically port map the router the computer is directly connected to. Any others in between this router and your modem will have to be <a href="pfrouter.html">forwarded manually</a>. For detailed instructions, <a href="http://www.portforward.com/help/doublerouterportforwarding.htm">click here</a>.
|
||||
|
||||
<p>Finally make sure the OS X firewall is either disabled, or you have <a href="pffirewall.html">allowed Transmission's port</a>.
|
||||
<p>Finally make sure the macOS firewall is either disabled, or you have <a href="pffirewall.html">allowed Transmission's port</a>.
|
||||
The firewall can cause the port to remain closed, even if it has been successfully mapped by the router(s).
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ BUILDING ON WINDOWS
|
|||
rb07 has a writeup of this on the Transmission wiki:
|
||||
https://trac.transmissionbt.com/wiki/BuildingTransmissionQtWindows
|
||||
|
||||
BUILDING ON OS X
|
||||
BUILDING ON MACOS
|
||||
|
||||
nnc has a writeup of this on the Transmission wiki:
|
||||
https://trac.transmissionbt.com/wiki/BuildingTransmissionQtMac
|
||||
|
|
|
|||
Loading…
Reference in New Issue