From owner-freebsd-doc@FreeBSD.ORG Tue Aug 26 21:25:18 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E93D722D; Tue, 26 Aug 2014 21:25:17 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id C94CC3FF5; Tue, 26 Aug 2014 21:25:17 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 8DEB0D84; Tue, 26 Aug 2014 21:25:17 +0000 (UTC) Date: Tue, 26 Aug 2014 21:25:16 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@freebsd.org, freebsd-doc@freebsd.org, gjb@FreeBSD.org, wblock@FreeBSD.org Message-ID: <1481289350.11.1409088317269.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Build failed in Jenkins: FreeBSD_DOC #655 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_DOC X-Jenkins-Result: FAILURE X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2014 21:25:18 -0000 See Changes: [gjb] Add the script I used to find manual pages missing from head/share/xml/man-refs.ent. Sponsored by: The FreeBSD Foundation [gjb] Add more missing manual pages from head/, stable/10/, and stable/9/ that were excluded from the previous change because of local make.conf(5) and src.conf(5) entries. Sponsored by: The FreeBSD Foundation [wblock] Be more specific about necessary configuration when using Xorg in a VirtualBox FreeBSD guest. PR: 190829 Submitted by: Steven Doerfler [gjb] Add missing manual pages to man-refs.ent. This commit covers missing manual pages from the head/, stable/10/, and stable/9/ branches. Sponsored by: The FreeBSD Foundation ------------------------------------------ [...truncated 2988 lines...] devices are supported by &man.sio.4;, &man.ng.h4.4;, and ^ :2312: parser error : Entity 'man.hcseriald.8' not defined &man.hcseriald.8;. ^ :2316: parser error : Entity 'man.ng.ubt.4' not defined device uses the &man.ng.ubt.4; driver: ^ :2368: parser error : Entity 'man.ng.hci.4' not defined to &man.ng.hci.4;. ^ :2374: parser error : Entity 'man.hccontrol.8' not defined &man.hccontrol.8;. The example below shows how to find out ^ :2456: parser error : Entity 'man.hcsecd.8' not defined The &man.hcsecd.8; daemon is responsible for handling ^ :2473: parser error : Entity 'man.hcsecd.8' not defined switch forces &man.hcsecd.8; to stay in ^ :2485: parser error : Entity 'man.hcsecd.8' not defined /etc/rc.conf to configure &man.hcsecd.8; ^ :2490: parser error : Entity 'man.hcsecd.8' not defined The following is a sample of the &man.hcsecd.8; daemon ^ :2518: parser error : Entity 'man.ppp.8' not defined In &os;, these profiles are implemented with &man.ppp.8; ^ :2519: parser error : Entity 'man.rfcomm.pppd.8' not defined and the &man.rfcomm.pppd.8; wrapper which converts a ^ :2524: parser error : Entity 'man.rfcomm.pppd.8' not defined &man.rfcomm.pppd.8; for examples. ^ :2526: parser error : Entity 'man.rfcomm.pppd.8' not defined In this example, &man.rfcomm.pppd.8; is used to open a ^ :2538: parser error : Entity 'man.rfcomm.pppd.8' not defined hand, and in this case &man.rfcomm.pppd.8; will not perform ^ :2539: parser error : Entity 'man.sdpcontrol.8' not defined the SDP query. Use &man.sdpcontrol.8; to ^ :2545: parser error : Entity 'man.sdpd.8' not defined &man.sdpd.8; must be running and a new entry for ^ :2548: parser error : Entity 'man.rfcomm.pppd.8' not defined &man.rfcomm.pppd.8; for examples. Finally, start the ^ :2599: parser error : Entity 'man.ng.l2cap.4' not defined &man.ng.l2cap.4;. ^ :2601: parser error : Entity 'man.l2ping.8' not defined A useful command is &man.l2ping.8;, which can be used to ^ :2612: parser error : Entity 'man.l2control.8' not defined The &man.l2control.8; utility is used to perform various ^ :2630: parser error : Entity 'man.l2control.8' not defined the same logical connection as &man.l2control.8; ^ :2720: parser error : Entity 'man.sdpd.8' not defined &man.sdpd.8;, and command line client, &man.sdpcontrol.8;, ^ :2720: parser error : Entity 'man.sdpcontrol.8' not defined &man.sdpd.8;, and command line client, &man.sdpcontrol.8;, ^ :2761: parser error : Entity 'man.sdpd.8' not defined with the &man.sdpd.8; server. The following line can be ^ :2766: parser error : Entity 'man.sdpd.8' not defined Then the &man.sdpd.8; daemon can be started with: ^ :2773: parser error : Entity 'man.rfcomm.pppd.8' not defined example of such an application is &man.rfcomm.pppd.8;. Once ^ :2832: parser error : Entity 'man.sdpd.8' not defined service, &man.sdpd.8; must be running and a root folder, ^ :2974: parser error : Entity 'man.bpf.4' not defined &man.bpf.4; and &man.tcpdump.1; on the bridge interface or ^ :2985: parser error : Entity 'man.tap.4' not defined EtherIP tunnel or a &man.tap.4; based solution such as ^ :3001: parser error : Entity 'man.if.bridge.4' not defined bridge using &man.if.bridge.4;. A netgraph bridging driver is ^ :3002: parser error : Entity 'man.ng.bridge.4' not defined also available, and is described in &man.ng.bridge.4;. ^ :3006: parser error : Entity 'man.pfil.9' not defined that hooks into the &man.pfil.9; framework. The bridge can be ^ :3007: parser error : Entity 'man.altq.4' not defined used as a traffic shaper with &man.altq.4; or ^ :3008: parser error : Entity 'man.dummynet.4' not defined &man.dummynet.4;. ^ :3014: parser error : Entity 'man.if.bridge.4' not defined In &os;, &man.if.bridge.4; is a kernel module which is ^ :3015: parser error : Entity 'man.ifconfig.8' not defined automatically loaded by &man.ifconfig.8; when creating a ^ :3083: parser error : Entity 'man.ipfw.8' not defined and layer2 firewalling with &man.ipfw.8;. See ^ :3084: parser error : Entity 'man.if.bridge.4' not defined &man.if.bridge.4; for more information. ^ :3109: parser error : Entity 'man.ifconfig.8' not defined using &man.ifconfig.8;. For a bridge with ^ :3161: parser error : Entity 'man.ifconfig.8' not defined parameters is described in &man.ifconfig.8;. ^ :3256: parser error : Entity 'man.bpf.4' not defined packets are discarded after &man.bpf.4; processing and are not ^ :3259: parser error : Entity 'man.bpf.4' not defined &man.bpf.4; stream. This is useful for reconstructing the ^ :3286: parser error : Entity 'man.snmp.bridge.3' not defined &man.bsnmpd.1; and &man.snmp.bridge.3; for more information. ^ :3398: parser error : Entity 'man.lagg.4' not defined &os; provides the &man.lagg.4; interface which can be used ^ :3411: parser error : Entity 'man.lagg.4' not defined protocols are supported by &man.lagg.4;: ^ :3494: parser error : Entity 'man.fxp.4' not defined This example connects two &man.fxp.4; Ethernet ^ :3524: parser error : Entity 'man.lagg.4' not defined On the &os; system, create the &man.lagg.4; interface ^ :3591: parser error : Entity 'man.lagg.4' not defined interfaces are up, then create the &man.lagg.4; interface. ^ :3641: parser error : Entity 'man.lagg.4' not defined &man.lagg.4;, it is possible to configure a failover which ^ :3684: parser error : Entity 'man.lagg.4' not defined is up, then create the &man.lagg.4; interface with ^ :3804: parser error : Entity 'man.diskless.8' not defined boot into &os;. Refer to &man.diskless.8; for more ^ :3874: parser error : Entity 'man.inetd.8' not defined Enable &man.inetd.8; by adding the following line to ^ :3897: parser error : Entity 'man.inetd.8' not defined Start &man.inetd.8;: ^ :3962: parser error : Entity 'man.sshd.config.5' not defined is documented in &man.sshd.config.5;. ^ :3970: parser error : Entity 'man.vipw.8' not defined the password file with &man.vipw.8;. ^ :4258: parser error : Entity 'man.pxeboot.8' not defined &man.pxeboot.8;, which then loads the kernel. ^ :4281: parser error : Entity 'man.tftpd.8' not defined The BUGS sections in &man.tftpd.8; ^ :4458: parser error : Entity 'man.ifconfig.8' not defined use &man.ifconfig.8;: ^ :4581: parser error : Entity 'man.rtsol.8' not defined router solicitation daemon, &man.rtsol.8;. ^ :4686: parser error : Entity 'man.rtadvd.8' not defined This section demonstrates how to setup &man.rtadvd.8; to ^ :4689: parser error : Entity 'man.rtadvd.8' not defined To enable &man.rtadvd.8;, add the following to ^ :4696: parser error : Entity 'man.rtadvd.8' not defined to tell &man.rtadvd.8; to use ^ :5104: parser error : Entity 'man.sysctl.8' not defined via several &man.sysctl.8; variables documented in the ^ :5105: parser error : Entity 'man.carp.4' not defined &man.carp.4; manual pages. Other actions can be triggered ^ :5107: parser error : Entity 'man.devd.8' not defined &man.devd.8;. ^ :5193: parser error : chunk is not well balanced ^ :292: parser error : Failure to process entity chap.advanced-networking &chap.advanced-networking; ^ :292: parser error : Entity 'chap.advanced-networking' not defined &chap.advanced-networking; ^ :380: parser error : Entity 'man.jail.8' not defined Discussion about the &man.jail.8; ^ :551: parser error : Entity 'man.sysinstall.8' not defined &man.sysinstall.8; development ^ :2388: parser error : chunk is not well balanced ^ :301: parser error : Failure to process entity chap.eresources &chap.eresources; ^ :301: parser error : Entity 'chap.eresources' not defined &chap.eresources; ^ :453: parser error : Entity 'man.crypt.3' not defined method of encryption for &unix; passwords and the &man.crypt.3; ^ :951: parser error : Entity 'man.witness.4' not defined (but removed for releases), called &man.witness.4;, ^ :953: parser error : Entity 'man.witness.4' not defined (&man.witness.4; is actually slightly conservative, so ^ :2031: parser error : chunk is not well balanced ^ :304: parser error : Failure to process entity chap.freebsd-glossary &chap.freebsd-glossary; ^ :304: parser error : Entity 'chap.freebsd-glossary' not defined &chap.freebsd-glossary; ^ *** [book.parsed.xml] Error code 1 Stop in *** [all] Error code 1 Stop in *** [all] Error code 1 Stop in *** [all] Error code 1 Stop in Build step 'Execute shell' marked build as failure