MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Using_filesystem_access_controls",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "12": {
                "pageid": 12,
                "ns": 0,
                "title": "Using JFileServer Enterprise From The Command Line",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "To run JFileServer Enterprise from the command line you first need to download the latest JFileServer Enterprise Kit zip file from [http://www.filesys.org/kits/jfileserver-enterprise/ here].\n\nUnpack the JFileServer Enterprise Kit zip file into a new folder. You should now have a folder with the following files and folders :-\n\n /jfileserver\n  |\n  +- /testShare\n      |\n      +- sharedFile.txt\n  +- /lib\n      |\n      +- bcprov-jdk5on-1.48.jar\n      +- hazelcast-3.10.1.jar\n      +- jfileserver-1.1.1.jar\n      +- jna-5.1.0.jar\n      +- jna-platform-5.1.0.jar\n  +- /licence\n      +- README.txt\n      +- jfileserver.lic\n  +- /licencing\n      +- BouncyCastle.txt\n      +- Hazelcast.txt\n      +- JFileServer.txt\n      +- JNA.txt\n  +- EULA.txt\n  +- fileSrvConfig.xml\n  +- fileSrvConfig-windows.xml\n  +- port445.reg\n  +- runsrv.bat\n  +- runsrv.sh\n\nThe included scripts, runsrv.bat for Windows and runsrv.sh for Unix platforms, start JFileServer Enterprise using the main class ''org.filesys.app.EnterpriseFileServer''. The JFileServer Enterprise application requires a single command line parameter with the path to the XML configuration file.\n\n== Using JFileServer Enterprise On Windows ==\nOn Windows it is recommended to use the Docker image to run JFileServer Enterprise due to problems with the Windows OS already using the native SMB port 445. Details of how to use the JFileServer Enterprise Docker image is available [[Using the JFileServer Enterprise Docker Image|here]].\n\n== Using JFileServer Enterprise on linux, macOS, Unix ==\nOn linux, macOS and Unix systems the default JFileServer Enterprise configuration runs the SMB server using native SMB but via the non-privileged port 1445, so that JFileServer Enterprise can be run using a normal user account. To run JFileServer Enterprise on port 445 would require running JFileServer Enteprise using the root user.\n\nIn order for SMB clients to be able to connect to the JFileServer SMB server when it is running on a non-privileged port we need to use the firewall to forward network packets from the default port of 445, that the client will connect to, to port 1445 that the JFileServer SMB server is listening on.\n\n=== Setting Up Port Forwarding On Linux ===\nOn linux kernel firewall rules are used to forward network packets. The firewall rules are configured using the ''iptables'' command.\n\nTo enable forwarding of network traffic from port 445 to port 1445 :-\n* Enable network forwarding\n echo 1 > /proc/sys/net/ipv4/ip_forward\n* Load the iptable_nat module\n modprobe iptable_nat\n* Configure the firewall forwarding rule\n iptables -F\n iptables -t nat -F\n iptables -P INPUT ACCEPT\n iptables -P FORWARD ACCEPT\n iptables -P OUTPUT ACCEPT\n iptables -t nat -A PREROUTING -p tcp --dport 445 -j REDIRECT --to-ports 1445\n\n=== Setting Up Port Forwarding On macOS ===\nOn more recent versions of macOS (10.10 onwards) the packet filter device is used to control forwarding of network packets. The packet filter is configured using the ''/etc/pf.conf'' file and associated files in the ''/etc/pf.anchors'' folder.\n\nTo enable forwarding of network traffic from port 445 to port 1445. :-\n* Edit the ''/etc/pf.conf'' file, add the lines in bold.  You will need to run the editor using the ''sudo'' command.\n\n #\n # com.apple anchor point\n #\n scrub-anchor \"com.apple/*\"\n nat-anchor \"com.apple/*\"\n rdr-anchor \"com.apple/*\"\n '''rdr-anchor \"org.filesys\"'''\n dummynet-anchor \"com.apple/*\"\n anchor \"com.apple/*\"\n \n load anchor \"com.apple\" from \"/etc/pf.anchors/com.apple\"\n '''load anchor \"org.filesys\" from \"/etc/pf.anchors/org.filesys\"'''\n\n* Create the ''org.filesys'' anchor file in the ''/etc/pf.anchors'' folder, add the following line :-\n rdr pass on en0 inet proto tcp from any to any port 445 -> 127.0.0.1 port 1445\n\n* Enable the port 445 forwarding rules using :-\n\n sudo pfctl -e -f /etc/pf.conf -v\n\n=== Running JFileServer Enerprise ===\nUsing a command line terminal or shell set your current working directory as the JFileServer directory.\n\nJFileServer Enterprise requires a licence file to enable the Enterprise features, there is a time limited trial licence included in the JFileServer Enterprise kit in the ''licence/'' folder. If you have purchased your own licence you should copy the licence file into the ''licence/'' folder, the default name for the licence file is ''jfileserver.lic''. The location and name of the licence file can be changed in the XML server configuration file.\n\nThere is a default JFileServer Enterprise configuration file that configures the SMB server to use SMB2 and will share the ''testShare'' folder, which contains a single text file. For details on configuring JFileServer see [[Configuring JFileServer|here]].\n\nTo start JFileServer Enteprise use the ''runsrv.sh'' script file :-\n\n ./runsrv.sh\n\nThe default JFileServer Enterprise configuration will output debug logging to the console, on startup of the server you should see the following :-\n\n Enterprise JFileServer starting, enter 'x' to shutdown server, 'r' to restart server ...\n *** JFileServer Enterprise edition licenced to FileSys.Org (Evaluation/eval@filesys.org/5)\n ***  For version 1.*\n ***  Licence expires in 60 days, at Mon Mar 11 12:05:34 GMT 2019\n Starting server SMB ...\n [SMB] SMB Server JFILESRV starting\n [SMB] Version 1.0.0, Java VM 25.152-b16, OS Mac OS X, version 10.14.2\n [SMB] Using authenticator org.filesys.server.auth.EnterpriseSMBAuthenticator, mode=USER\n [SMB] Server timezone offset = 0hrs\n [SMB] Dialects enabled = [SMB 2.002,SMB 2.210,SMB 2.ANY]\n [SMB] Shares:\n [SMB]  [JFILESHARE,DISK,,[./testShare]] [./testShare]\n [SMB] Binding TCP-SMB session handler to address : ALL\n [SMB] Request handler SMBRequestHandler_1 waiting for session ...\n [SMB] Listening for connections on [SMB,TCP-SMB,ALL:1445]\n [SMB] Waiting for new connection ...\n\nTo stop the running JFileServer enter ''x'' into the console and hit <Return>, the file server should shutdown within a few seconds, but may take up to a minute or so :-\n\n x\n Shutting server SMB ...\n [SMB] SMB Server shutting down ...\n [SMB] Packet pool at shutdown: [BufferLists: [Bufsize=256,Init=20,Max=100,Avail=20,Alloc=0,Stats=0/0/0] [Bufsize=4096,Init=20,Max=50,Avail=20,Alloc=0,Stats=0/0/0] [Bufsize=16384,Init=5,Max=50,Avail=5,Alloc=0,Stats=0/0/0]  [Bufsize=66000,Init=5,Max=50,Avail=5,Alloc=0,Stats=0/0/0] ]\n Shutting server NetBIOS ...\n [SMB] Closed session handler [SMB,TCP-SMB,ALL:1445]\n [SMB] Closed request handler, SMBRequestHandler_1\n [SMB] Closed SMB request handler, SMBRequestHandler_1\n NotifyChangeHandler thread exit"
                    }
                ]
            },
            "11": {
                "pageid": 11,
                "ns": 0,
                "title": "Using JFileServer From The Command Line",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "To run JFileServer from the command line you first need to download the latest JFileServer Kit zip file from [http://www.filesys.org/kits/jfileserver/ here].\n\nUnpack the JFileServer Kit zip file into a new folder. You should now have a folder with the following files and folders :-\n\n /jfileserver\n  |\n  +- /testShare\n      |\n      +- sharedFile.txt\n  +- /lib\n      |\n      +- bcprov-jdk5on-1.48.jar\n      +- hazelcast-3.10.1.jar\n      +- jfileserver-1.1.1.jar\n      +- jna-5.1.0.jar\n      +- jna-platform-5.1.0.jar\n  +- /licencing\n      +- BouncyCastle.txt\n      +- Hazelcast.txt\n      +- JNA.txt\n  +- fileSrvConfig.xml\n  +- fileSrvConfig-windows.xml\n  +- LICENSE\n  +- port445.reg\n  +- runsrv.bat\n  +- runsrv.sh\n\nThe included scripts, runsrv.bat for Windows and runsrv.sh for Unix platforms, start JFileServer using the main class ''org.filesys.app.FileServer''. The JFileServer application requires a single command line parameter with the path to the XML configuration file.\n\n== Using JFileServer On Windows ==\nOn Windows it is recommended to use the Docker image to run JFileServer due to problems with the Windows OS already using the native SMB port 445. Details of how to use the JFileServer Docker images is available [[Using the JFileServer Docker Images|here]].\n\n== Using JFileServer on linux, macOS, Unix ==\nOn linux, macOS and Unix systems the default JFileServer configuration runs the SMB server using native SMB but via the non-privileged port 1445, so that JFileServer can be run using a normal user account. To run JFileServer on port 445 would require running JFileServer using the root user.\n\nIn order for SMB clients to be able to connect to the JFileServer SMB server when it is running on a non-privileged port we need to use the firewall to forward network packets from the default port of 445, that the client will connect to, to port 1445 that the JFileServer SMB server is listening on.\n\n=== Setting Up Port Forwarding On Linux ===\nOn linux kernel firewall rules are used to forward network packets. The firewall rules are configured using the ''iptables'' command.\n\nTo enable forwarding of network traffic from port 445 to port 1445 :-\n* Enable network forwarding\n echo 1 > /proc/sys/net/ipv4/ip_forward\n* Load the iptable_nat module\n modprobe iptable_nat\n* Configure the firewall forwarding rule\n iptables -F\n iptables -t nat -F\n iptables -P INPUT ACCEPT\n iptables -P FORWARD ACCEPT\n iptables -P OUTPUT ACCEPT\n iptables -t nat -A PREROUTING -p tcp --dport 445 -j REDIRECT --to-ports 1445\n\n=== Setting Up Port Forwarding On macOS ===\nOn more recent versions of macOS (10.10 onwards) the packet filter device is used to control forwarding of network packets. The packet filter is configured using the ''/etc/pf.conf'' file and associated files in the ''/etc/pf.anchors'' folder.\n\nTo enable forwarding of network traffic from port 445 to port 1445. :-\n* Edit the ''/etc/pf.conf'' file, add the lines in bold.  You will need to run the editor using the ''sudo'' command.\n\n #\n # com.apple anchor point\n #\n scrub-anchor \"com.apple/*\"\n nat-anchor \"com.apple/*\"\n rdr-anchor \"com.apple/*\"\n '''rdr-anchor \"org.filesys\"'''\n dummynet-anchor \"com.apple/*\"\n anchor \"com.apple/*\"\n \n load anchor \"com.apple\" from \"/etc/pf.anchors/com.apple\"\n '''load anchor \"org.filesys\" from \"/etc/pf.anchors/org.filesys\"'''\n\n* Create the ''org.filesys'' anchor file in the ''/etc/pf.anchors'' folder, add the following line :-\n rdr pass on en0 inet proto tcp from any to any port 445 -> 127.0.0.1 port 1445\n\n* Enable the port 445 forwarding rules using :-\n\n sudo pfctl -e -f /etc/pf.conf -v\n\n=== Running JFileServer ===\nUsing a command line terminal or shell set your current working directory as the JFileServer directory.\n\nThere is a default JFileServer configuration file that will share the ''testShare'' folder, which contains a single text file. For details on configuring JFileServer see [[Configuring JFileServer|here]].\n\nTo start JFileServer use the ''runsrv.sh'' script file :-\n\n ./runsrv.sh\n\nThe default JFileServer configuration will output debug logging to the console, on startup of the server you should see the following :-\n\n JFileServer starting, enter 'x' to shutdown server, 'r' to restart server ...\n Starting server SMB ...\n [SMB] SMB Server JFILESRV starting\n [SMB] Version 1.0.0, Java VM 25.152-b16, OS Mac OS X, version 10.14.2\n [SMB] Using authenticator org.filesys.server.auth.EnterpriseSMBAuthenticator, mode=USER\n [SMB] Server timezone offset = 0hrs\n [SMB] Dialects enabled = [Core,CorePlus,DOS LANMAN 1.0,LANMAN1.0,DOS LANMAN 2.1,LM1.2X002,LANMAN2.1,NT LM 0.12]\n [SMB] Shares:\n [SMB]  [JFILESHARE,DISK,,[./testShare]] [./testShare]\n [SMB] Added NTServer flag to host announcement\n [SMB] Binding TCP-SMB session handler to address : ALL\n [SMB] Binding NetBIOS session handler to address : ALL\n [SMB] Request handler SMBRequestHandler_1 waiting for session ...\n [SMB] Listening for connections on [SMB,TCP-SMB,ALL:1445]\n [SMB] Waiting for new connection ...\n\nTo stop the running JFileServer enter ''x'' into the console and hit <Return>, the file server should shutdown within a few seconds, but may take up to a minute or so :-\n\n x\n Shutting server SMB ...\n [SMB] SMB Server shutting down ...\n [SMB] Packet pool at shutdown: [BufferLists: [Bufsize=256,Init=20,Max=100,Avail=20,Alloc=0,Stats=0/0/0] [Bufsize=4096,Init=20,Max=50,Avail=20,Alloc=0,Stats=0/0/0] [Bufsize=16384,Init=5,Max=50,Avail=5,Alloc=0,Stats=0/0/0]  [Bufsize=66000,Init=5,Max=50,Avail=5,Alloc=0,Stats=0/0/0] ]\n Shutting server NetBIOS ...\n [SMB] Closed session handler [SMB,TCP-SMB,ALL:1445]\n [SMB] Closed request handler, SMBRequestHandler_1\n [SMB] Closed SMB request handler, SMBRequestHandler_1\n NotifyChangeHandler thread exit"
                    }
                ]
            }
        }
    }
}