1) stop ts3server
2) bash ts3server_minimal_runscript.sh serveradmin_password=new_password
3) telnet 127.0.0.1 10011
4)
login serveradmin new_password
use port=9987
tokenadd tokentype=0 tokenid1=6 tokenid2=0
le '6' est l'id du groupe serveradmin qui peut changer... checker dans le client dans les permissions, on peut voir l'id dans les groupes de serveurs
5) Copier/coller le token dans le client et bam ça fait des chocapic !
-
https://links.infomee.fr/?kX2n7Qencore un article qui plébiscite vue
-
http://sametmax.com/vue-jlavais-pas-vu/
-
https://links.infomee.fr/?Vp7r6QPourquoi pas pour la voiture
-
https://mobile.audible.fr/Add /json to pypi package url.. Magic!
-
https://pypi.python.org/pypi/awscli/jsonExactement ce que je cherchais
You can use the mysql_config_editor utility to store authentication credentials in an encrypted login path file named .mylogin.cnf.
To create a new set of credentials run:
mysql_config_editor set --host=db.host.org --user=dbuser --password
and enter your password when prompted.
This will store your authentication credentials in the default client login path.
You can store multiple authentication credentials by specifying a different --login-path option:
mysql_config_editor set --login-path=db2 --host=db2.host.org --user=dbuser --password
By default, the mysql client reads the [client] and [mysql] groups from other option files, so it reads them from the login path file as well. With a --login-path option, client programs additionally read the named login path from the login path file. The option groups read from other option files remain the same. Consider this command:
mysql --login-path=db2
The mysql client reads [client] and [mysql] from other option files, and [client], [mysql], and [mypath] from the login path file.
To print out all the information stored in the configuration file run:
mysql_config_editor print --all=true
More information about the utility can be found at "mysql_config_editor — MySQL Configuration Utility".
-
https://dev.mysql.com/doc/refman/5.7/en/mysql-config-editor.html
-
https://links.infomee.fr/?kmGPewIf you enable s3 enpoint in your route table, it's kind of tricky to know if the endpoint is really working. Two things to validate:
1) traceroute tcp before and after (traceroute -T s3-us-west-1.amazonaws.com 443)
You will see more hope when endpoint not activated
2) try an s3 sync cross region with enpoint activated : it should failed since it's not supported (yet @ 2017-05-02)
-
https://links.infomee.fr/?1wF2Kg:Glog
:clist
:cprev
:cnext
:cfirst
:clast
-
http://vimcasts.org/episodes/fugitive-vim-exploring-the-history-of-a-git-repository/