- discuss - lists.mariadb.org

[Maria-discuss] MariaDB 5.5.52 now available
by Daniel Bartholomew 13 Sep '16

13 Sep '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.52 Stable (GA). See the Release Notes and Changelog for details. IMPORTANT: There was a security fix included in the 5.5.51 release of MariaDB. If you are running MariaDB 5.5.50 or lower, please upgrade to at least MariaDB 5.5.51 right away. See the MariaDB 5.5.51 release notes and the following blog post for more details. - https://mariadb.org/mariadb-server-versions-remote-root-code-execution-vuln… - https://mariadb.com/kb/en/mariadb-5551-release-notes/ - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 5.5.52 Stable (GA) - Release Notes: https://mariadb.com/kb/en/mdb-5552-rn/ - Changelog: https://mariadb.com/kb/en/mdb-5552-cl/ - Downloads: https://downloads.mariadb.org/mariadb/5.5.52 About MariaDB 5.5: - https://mariadb.com/kb/en/what-is-mariadb-55/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 1.5.0 RC - Release Notes: https://mariadb.com/kb/en/mcj-150-rn/ - Changelog: https://mariadb.com/kb/en/mcj-150-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.5.0/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/C 2.3.1 - Release Notes: https://mariadb.com/kb/en/mcc-231-rn/ - Changelog: https://mariadb.com/kb/en/mcc-231-cl/ - Downloads: https://downloads.mariadb.org/connector-c/2.3.1/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf or my.ini file! See http://mariadb.com/kb/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: - http://mariadb.org/jira - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Critical Update for CVE-2016-6662
by Alex 13 Sep '16

13 Sep '16

Hello, In regards to this zero day remote exploit , it seems MariaDB is also affected. Percona seems to have released new versions out to fix this. Any news from MariaDB side ? http://legalhackers.com/advisories/MySQL-Exploit-Remote-Root-Code-Execution… Regards, Alexandru

5 16

[Maria-discuss] MariaDB Developers Meetup
by Ian Gilfillan 12 Sep '16

12 Sep '16

The MariaDB Developers Meetup in Amsterdam is less than a month away now (October 6-8), and we're starting to set the schedule. If you want to suggest a topic to be covered, please add it now at https://docs.google.com/spreadsheets/d/1D7yS8wgCQVXNSEzuIjtAOGfyVwJStUoEb23… - you can also vote for those sessions you'd most be interested in. Full details of the meetup are at https://mariadb.org/2016-mariadb-developers-meetup/ - remember to sign up on the Meetup group as well to let us know you'll be coming.

1 0

[Maria-discuss] Database Platform Migration
by Suresh Rajagopal 10 Sep '16

10 Sep '16

Hi, How to migrate mysql 5.0 database from darwin to Linux? Database size is close to 1 TB Thanks Suresh Rajagopal

1 0

[Maria-discuss] Spider Nodes
by Suresh Rajagopal 10 Sep '16

10 Sep '16

Hi, What is best place to keep spider nodes ? Dedicated Physical Servers or Virtual Machines or Backend Nodes Backend nodes are physical servers with SSD. ThanksSuresh Rajagopal

1 0

[Maria-discuss] Reg Audit Trail Implementation
by Karthick Subramanian 08 Sep '16

08 Sep '16

All, Before I reinvent a wheel again, thought of checking with you experts whether any recommendation or suggestion for implementing audit trail feature for your database. I am looking for any open source product/tool for this purpose. I thought of exploring audit plugin, but I am not sure whether we can enable audit trail for the data changes in a tables. For example: *ORDER table:* ORDER_ID PRODUCT_ID QTY ORDER_DATE SHIP_DATE DELIVERY_DATE DELIVERY_ADDRESS Any changes on the above table's data (rows), we need to capture the audit trail like TABLE_NAME,COLUMN_NAME,OLD_VALUE,NEW_VALUE,CHANGE_DATE,CHANGE_BY,HOST,APP,MODULE etc. Thank you, Karthick

2 1

[Maria-discuss] handling of mixed case roles
by Robin Peiremans 05 Sep '16

05 Sep '16

Hi I've created a role with both upper and lowercase name, resulting in some weird behavior (output and test case below). The first thing I noticed is that you can create roles with the same name but different case (test_role and test_ROLE in below example), but you can't grant both to the same user as that results in an error 1961 when granting the second role. Imo this indicates that not all the roles code is case-sensitive. The second weird thing is that when you get the error 1961 in above scenario, the first role (that was granted successfully) is gone from the show grants output. It is not revoked (the user can still use it), it just isn't shown anymore until I flush privileges. Can this be considered a bug, or am I missing something here? MariaDB version: 10.1.13-MariaDB OS: Red Hat 7.2 Kind regards Robin Output and test case: MariaDB [mysql]> create role test_ROLE; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> create role test_role; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> grant select on mysql.* to test_role; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> select user, host from user where is_role='y' and user like 'test%'; +-----------+------+ | user | host | +-----------+------+ | test_ROLE | | | test_role | | +-----------+------+ 2 rows in set (0.00 sec) MariaDB [mysql]> grant test_role to testuser; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> show grants for testuser; +------------------------------------------------------------------------+ | Grants for testuser@% | +------------------------------------------------------------------------+ | GRANT test_role TO 'testuser'@'%' | | GRANT USAGE ON *.* TO 'testuser'@'%' IDENTIFIED VIA pam USING 'mariadb' | +------------------------------------------------------------------------+ 2 rows in set (0.00 sec) MariaDB [mysql]> grant test_ROLE to testuser; ERROR 1961 (HY000): Cannot grant role 'test_ROLE' to: 'testuser'. MariaDB [mysql]> show grants for testuser; +------------------------------------------------------------------------+ | Grants for testuser@% | +------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'testuser'@'%' IDENTIFIED VIA pam USING 'mariadb' | +------------------------------------------------------------------------+ 1 row in set (0.00 sec) MariaDB [mysql]> select * from roles_mapping where user='testuser'; +-----------+---------+-----------+--------------+ | Host | User | Role | Admin_option | +-----------+---------+-----------+--------------+ | % | testuser | test_role | N | +-----------+---------+-----------+--------------+ 3 rows in set (0.00 sec) MariaDB [mysql]> flush privileges; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> show grants for testuser; +------------------------------------------------------------------------+ | Grants for testuser@% | +------------------------------------------------------------------------+ | GRANT test_role TO 'testuser'@'%' | | GRANT USAGE ON *.* TO 'testuser'@'%' IDENTIFIED VIA pam USING 'mariadb' | +------------------------------------------------------------------------+ 2 rows in set (0.00 sec) This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify KBC immediately and then delete this e-mail. KBC does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of or reliance on the information. All e-mail messages addressed to, received or sent by KBC or KBC employees are deemed to be professional in nature. Accordingly, the sender or recipient of these messages agrees that they may be read by other KBC employees than the official recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof.

2 2

[Maria-discuss] R: handling of mixed case roles
by Federico Razzoli 05 Sep '16

05 Sep '16

Users are case-sensitive, so I expect the same from roles. If something doesn't work with mixed-case roles, it is probably a bug. Federico -------------------------------------------- Lun 5/9/16, Robin Peiremans <robin.peiremans(a)kbc.be> ha scritto: Oggetto: [Maria-discuss] handling of mixed case roles A: "maria-discuss(a)lists.launchpad.net" <maria-discuss(a)lists.launchpad.net> Data: Lunedì 5 settembre 2016, 10:27 Hi I've created a role with both upper and lowercase name, resulting in some weird behavior (output and test case below). The first thing I noticed is that you can create roles with the same name but different case (test_role and test_ROLE in below example), but you can't grant both to the same user as that results in an error 1961 when granting the second role. Imo this indicates that not all the roles code is case-sensitive. The second weird thing is that when you get the error 1961 in above scenario, the first role (that was granted successfully) is gone from the show grants output. It is not revoked (the user can still use it), it just isn't shown anymore until I flush privileges. Can this be considered a bug, or am I missing something here? MariaDB version: 10.1.13-MariaDB OS: Red Hat 7.2 Kind regards Robin Output and test case: MariaDB [mysql]> create role test_ROLE; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> create role test_role; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> grant select on mysql.* to test_role; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> select user, host from user where is_role='y' and user like 'test%'; +-----------+------+ | user | host | +-----------+------+ | test_ROLE | | | test_role | | +-----------+------+ 2 rows in set (0.00 sec) MariaDB [mysql]> grant test_role to testuser; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> show grants for testuser; +------------------------------------------------------------------------+ | Grants for testuser@% | +------------------------------------------------------------------------+ | GRANT test_role TO 'testuser'@'%' | | GRANT USAGE ON *.* TO 'testuser'@'%' IDENTIFIED VIA pam USING 'mariadb' | +------------------------------------------------------------------------+ 2 rows in set (0.00 sec) MariaDB [mysql]> grant test_ROLE to testuser; ERROR 1961 (HY000): Cannot grant role 'test_ROLE' to: 'testuser'. MariaDB [mysql]> show grants for testuser; +------------------------------------------------------------------------+ | Grants for testuser@% | +------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'testuser'@'%' IDENTIFIED VIA pam USING 'mariadb' | +------------------------------------------------------------------------+ 1 row in set (0.00 sec) MariaDB [mysql]> select * from roles_mapping where user='testuser'; +-----------+---------+-----------+--------------+ | Host | User | Role | Admin_option | +-----------+---------+-----------+--------------+ | % | testuser | test_role | N | +-----------+---------+-----------+--------------+ 3 rows in set (0.00 sec) MariaDB [mysql]> flush privileges; Query OK, 0 rows affected (0.00 sec) MariaDB [mysql]> show grants for testuser; +------------------------------------------------------------------------+ | Grants for testuser@% | +------------------------------------------------------------------------+ | GRANT test_role TO 'testuser'@'%' | | GRANT USAGE ON *.* TO 'testuser'@'%' IDENTIFIED VIA pam USING 'mariadb' | +------------------------------------------------------------------------+ 2 rows in set (0.00 sec) Disclaimer -----Segue allegato----- _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

1 0

[Maria-discuss] mysqld syslog flood Bad file descriptor
by Raffael Sahli 05 Sep '16

05 Sep '16

Hi Over the weekend I had a problem with one mysqld instance. This single instance flooded our entire syslog infrastructure with ~190mio log entries within 6 hours. The messages was: "140289656219584 [ERROR] Error in accept: Bad file descriptor" mysqld: /usr/sbin/mysqld Ver 10.1.16-MariaDB-1~trusty for debian-linux-gnu on x86_64 (mariadb.org binary distribution) I will configure rsyslog to throttle such entries, but anyways, is this a known problem? Cheers -- Raffael Sahli public(a)raffaelsahli.com

1 0

[Maria-discuss] 回复：Re:__转发：failed_to_connect_mariadb_at_addition_node_in_MariaDB_galera_cluster
by 西门吹牛 03 Sep '16

03 Sep '16

Hi, Thanks for the reponse. No, I started mysqld on the second node via comamd "mysqld --defaults-extra-file=mdb.my.cnf --debug". The problem is permanent. No abnormal output seen from the console. I feel mariadb may stuck somewher. from the trace log(attached mdb.mysqld.trace). it looks stuck at wsrep_replication_process. It may wait for some message from primary node. but I have no ieda what it waits for. -------------------------------- ----- 原始邮件 ----- 发件人：Nirbhay Choubey <nirbhay(a)mariadb.com> 收件人：zh1029(a)sina.com 抄送人：maria-discuss <maria-discuss(a)lists.launchpad.net>, "yan-jack.chen" <yan-jack.chen(a)nokia.com> 主题：Re:_[Maria-discuss]_转发：failed_to_connect_mariadb_at_addition_node_in_MariaDB_galera_cluster 日期：2016年09月02日 23点26分 Hi, On Thu, Sep 1, 2016 at 11:08 PM, 西门吹牛 <zh1029(a)sina.com> wrote: Hi, I deployed two MariaDB galera version in two nodes to build cluster. But I can’t connect MariaDB in second node as seems the port is not created by MariaDB because looks like it is stuck somehow. Version: mysqld 10.1.17-MariaDB-debug VS galera-3-25.3.17 I started MariaDB in first node. Seems fine. Port 3307 was created and I can login Mariadb by mysql. You shouldn't use --wsrep-new-cluster to start the 2nd node (in case you are).Regarding the hang:Does it happen all the time? Repeatable?Is that all you see in the error log? Nothing after the partial last line?Will it be possible to attach mysqld to some debugger to check where exactly does it hang? Best,Nirbhay [root@MMN-0(RCP-69) /root/test] # /home/_rcpadmin/bin/mariadb/bin/mysqld --defaults-extra-file=./mmn.my.cnf --wsrep-new-cluster --debug 2016-09-01 16:41:37 140716544316288 [Note] /home/_rcpadmin/bin/mariadb/bin/mysqld (mysqld 10.1.17-MariaDB-debug) starting as process 15248 ... 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Setting wsrep_ready to 0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Read nil XID from storage engines, skipping position init 2016-09-01 16:41:38 140716544316288 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib64/libgalera_smm.so' 2016-09-01 16:41:38 140716544316288 [Note] WSREP: wsrep_load(): Galera 3.17(r0) by Codership Oy <info(a)codership.com> loaded successfully. 2016-09-01 16:41:38 140716544316288 [Note] WSREP: CRC-32C: using hardware acceleration. 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Found saved state: 900987cc-7003-11e6-b25f-de0a52317f1d:0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Passing config to GCS: base_dir = /mariadb/; base_host = MMN-0; base_port = 4567; cert.log_conflicts = no; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 4; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 2; evs.view_forget_timeout = PT24H; gcache.dir = /mariadb/; gcache.keep_pages_size = 0; gcache.mem_size = 0; gcache.name = /mariadb//galera.cache; gcache.page_size = 300M; gcache.size = 300M; gcomm.thread_prio = ; gcs.fc_debug = 0; gcs.fc_factor = 1.0; gcs.fc_limit = 16; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit = 9223372036854775807; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.version = 0; pc.announce_timeout = PT3S; pc.checksum = false; pc.ignore_quorum = false; pc.ignore_sb = false; pc 2016-09-01 16:41:38 140716029634304 [Note] WSREP: Service thread queue flushed. 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Assign initial position for certification: 0, protocol version: -1 2016-09-01 16:41:38 140716544316288 [Note] WSREP: wsrep_sst_grab() 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Start replication 2016-09-01 16:41:38 140716544316288 [Note] WSREP: 'wsrep-new-cluster' option used, bootstrapping the cluster 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Setting initial position to 900987cc-7003-11e6-b25f-de0a52317f1d:0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: protonet asio version 0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Using CRC-32C for message checksums. 2016-09-01 16:41:38 140716544316288 [Note] WSREP: backend: asio 2016-09-01 16:41:38 140716544316288 [Note] WSREP: gcomm thread scheduling priority set to other:0 2016-09-01 16:41:38 140716544316288 [Warning] WSREP: access file(/mariadb//gvwstate.dat) failed(No such file or directory) 2016-09-01 16:41:38 140716544316288 [Note] WSREP: restore pc from disk failed 2016-09-01 16:41:38 140716544316288 [Note] WSREP: GMCast version 0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: (e5a32d3c, 'tcp://0.0.0.0:4567') listening at tcp://0.0.0.0:4567 2016-09-01 16:41:38 140716544316288 [Note] WSREP: (e5a32d3c, 'tcp://0.0.0.0:4567') multicast: , ttl: 1 2016-09-01 16:41:38 140716544316288 [Note] WSREP: EVS version 0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: gcomm: bootstrapping new group 'example_cluster' 2016-09-01 16:41:38 140716544316288 [Note] WSREP: start_prim is enabled, turn off pc_recovery 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Node e5a32d3c state prim 2016-09-01 16:41:38 140716544316288 [Note] WSREP: view(view_id(PRIM,e5a32d3c,1) memb { e5a32d3c,0 } joined { } left { } partitioned { }) 2016-09-01 16:41:38 140716544316288 [Note] WSREP: save pc into disk 2016-09-01 16:41:38 140716544316288 [Note] WSREP: discarding pending addr without UUID: tcp://169.254.0.4:4567 2016-09-01 16:41:38 140716544316288 [Note] WSREP: discarding pending addr proto entry 0x5652b0352ef0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: discarding pending addr without UUID: tcp://169.254.0.5:4567 2016-09-01 16:41:38 140716544316288 [Note] WSREP: discarding pending addr proto entry 0x5652b035b720 2016-09-01 16:41:38 140716544316288 [Note] WSREP: discarding pending addr without UUID: tcp://169.254.0.6:4567 2016-09-01 16:41:38 140716544316288 [Note] WSREP: discarding pending addr proto entry 0x5652b0363ea0 2016-09-01 16:41:38 140716544316288 [Note] WSREP: gcomm: connected 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 0) 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Opened channel 'example_cluster' 2016-09-01 16:41:38 140715987670784 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 1 2016-09-01 16:41:38 140716544316288 [Note] WSREP: Waiting for SST to complete. 2016-09-01 16:41:38 140715987670784 [Note] WSREP: STATE_EXCHANGE: sent state UUID: e5a3bc45-701f-11e6-ba1c-471590fea490 2016-09-01 16:41:38 140715987670784 [Note] WSREP: STATE EXCHANGE: sent state msg: e5a3bc45-701f-11e6-ba1c-471590fea490 2016-09-01 16:41:38 140715987670784 [Note] WSREP: STATE EXCHANGE: got state msg: e5a3bc45-701f-11e6-ba1c-471590fea490 from 0 (MMN-0) 2016-09-01 16:41:38 140715987670784 [Note] WSREP: Quorum results: version = 4, component = PRIMARY, conf_id = 0, members = 1/1 (joined/total), act_id = 0, last_appl. = -1, protocols = 0/7/3 (gcs/repl/appl), group UUID = 900987cc-7003-11e6-b25f-de0a52317f1d 2016-09-01 16:41:38 140715987670784 [Note] WSREP: Flow-control interval: [16, 16] 2016-09-01 16:41:38 140715987670784 [Note] WSREP: Restored state OPEN -> JOINED (0) 2016-09-01 16:41:38 140715987670784 [Note] WSREP: Member 0.0 (MMN-0) synced with group. 2016-09-01 16:41:38 140716542806784 [Note] WSREP: New cluster view: global state: 900987cc-7003-11e6-b25f-de0a52317f1d:0, view# 1: Primary, number of nodes: 1, my index: 0, protocol version 3 2016-09-01 16:41:38 140715987670784 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 0) 2016-09-01 16:41:38 140716544316288 [Note] WSREP: SST complete, seqno: 0 2016-09-01 16:41:38 140716544316288 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-09-01 16:41:38 140716544316288 [Note] InnoDB: InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!! 2016-09-01 16:41:38 140716544316288 [Note] InnoDB: InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!! 2016-09-01 16:41:38 140716544316288 [Note] InnoDB: The InnoDB memory heap is disabled 2016-09-01 16:41:38 140716 _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

2 1