Problème de son avec Wiko Iggy



 

Hello, dès le début, le son étant faible, j’ai modifié à l’aide du menu ingénieur les niveaux de sorties audio, et le son est tout à fait correct en niveau et en qualité en liaison phonie…

voilà les niveaux que j’utilise :

NORMAL MODE : 155
HEADSET : 145
LOUDSPEAKER MODE : 150

(entrée menu ingénieur : *#*#3646633#*#* )
ne modifier que les données dans l’onglet « AUDIO » : « Max Vol 0-160 », ne pas toucher à « Value is 0~255…. »
ne rien toucher d’autre sous peine de « mauvaises » surprises…..


 

Vais te donner une astuce en espérant que je vais froisser personne mdr :whistle:

1- tu tapes comme si tu téléphonais a quelqu’un *#*#3646633#*#*

2- ensuite tu vas dans audio,

— headsetmode pour le volume des écouteurs,
monte la valeur Max Vol. entre 0 et 255 ensuite clic sur SET

— loudspeaker mode pour le son haut-parleur,
monte la valeur Max Vol. entre 0 et 255 ensuite clic sur SET

— speech enhancement pour améliorer discussion
etc etc à toi de faire les autres réglages

 

Messagerie Zimbra – outils pour dépanner


Hello,

I’ve install CentOS 6 (Basic server). ( … create a user other than root, configure a static ip address and update the system)
I’ve install dependencies :
[CODE]sudo yum install nc libidn gmp openssh[/CODE]

I’ve modified DNS configuration on my domain provider ( OVH ).
I made mistake : I first create a host with a name « mail » before changing it to the name of my zimbra server.

So the final DNS configuration is the following :
[CODE].mydomain.fr NS ns105.ovh.net
.mydomain.fr NS dns105.ovh.net
.mydomain.fr MX 10 myserver.mydomain.fr
.mydomain.fr A EXTERNAL.IP.OF.MYROUTER
www.mydomain.fr A EXTERNAL.IP.OF.MYROUTER
myserver.mydomain.fr A EXTERNAL.IP.OF.MYROUTER[/CODE]

I’ve configure my router to do NAT on port 25 to the local ip address of my zimbra server

I’ve install DNSMasq on the zimbra server for DNS SPLIT
/etc/dnsmasq.conf file :
[CODE]
server=8.8.8.8
server=208.67.222.222
domain=mydomain.fr
mx-host=mydomain.fr,myserver.mydomain.fr,5
listen-address=127.0.0.1
[/CODE]

/etc/hosts file :
[CODE]
127.0.0.1 localhost.localdomain localhost
192.168.1.8 myserver.mydomain.fr myserver
[/CODE]

/etc/resolv.conf file :
I know it shoud be :
[CODE]
search mydomain.fr
nameserver 127.0.0.1
[/CODE]

But the file is configured by DHCP whith these value :
[CODE]
; generated by /sbin/dhclient-script
nameserver 208.67.222.222
nameserver 208.67.220.220
[/CODE]

I put the install file ‘zcs-NETWORK-8.0.5_GA_5839.RHEL6_64.20130910124005.tgz’ and my XML licence in the home directory of the server.
I have untar and launch ‘./install.sh’ to start the installation.

I had error but was able to fix it ( I forget the hosts file … )
Finally, I configure the admin password, put the licence path and file name.

Then I run some test :
[CODE]su
su – zimbra
zmcontrol status[/CODE]

that gave me

[CODE][zimbra@myserver ~]$ zmcontrol status
Host myserver.mydomain.fr
antispam Running
antivirus Running
convertd Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Stopped
postfix is not running
opendkim Running
proxy Running
snmp Running
spell Running
stats Running
zmconfigd Running
[/CODE]

Even after doing
[CODE]
zmcontrol start
[/CODE]

I did some more testing :
[CODE][myuser@myserver ~]$ dig mydomain.fr mx

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.6 <<>> mydomain.fr mx
;; global options: +cmd
;; Got answer:
;; ->>HEADER< ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.fr. IN MX

;; ANSWER SECTION:
mydomain.fr. 1571 IN MX 1 mail.mydomain.fr.

;; Query time: 32 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Fri Nov 29 16:27:30 2013
;; MSG SIZE rcvd: 56
[/CODE]

Two things that are wrong :
This DNS server is still using my old hostname « mail » instead of « myserver » … I think I have to wait for world wide DNS replication.
The local machine is not using my local DNSMasq … may be because of the resolv.conf file. That have to be fix through the DHCP server.

——

Today, I’ve changed the network configuration to static IP on the server.
I’ve also tested the dig command. External DNS now give the correct host name.
But the internal DNS is not answering.
I check the /etc/resolv.conf. the file contain the necessary information.
I check the status of dnsmasq :
[CODE]
[myuser@myserver ~]$ sudo /etc/init.d/dnsmasq status
[sudo] password for myuser:
dnsmasq is stopped
[/CODE]
Ok, dnsmask is not starting at boot … I have to fix that

If I do
[CODE]
[myuser@myserver ~]$ su
Mot de passe :
[root@myserver myuser]# su – zimbra
[zimbra@myserver ~]$ zmcontrol start
[/CODE]

I get :

[CODE]
Starting mta…Failed.
Starting saslauthd…already running.
postfix failed to start
[/CODE]

In the zimbra.log file i get this error:

[CODE]
myserver postfix/master[4711]: fatal: bind 0.0.0.0 port 25: Address already in use
[/CODE]
[CODE]
[myuser@myserver ~]$ sudo lsof -i TCP:25
[sudo] password for myuser:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
master 1943 root 12u IPv4 14783 0t0 TCP localhost.localdomain:smtp (LISTEN)
master 1943 root 13u IPv6 14785 0t0 TCP localhost.localdomain:smtp (LISTEN)
[/CODE]

What that master process ?

That the system postfix. Weird, is-it install with the basic server centOS installation ?

[CODE]
[myuser@myserver ~]$ sudo /etc/init.d/postfix status
[sudo] password for myuser:
master (pid 1943) is running…
[/CODE]

So I stop it.
[CODE]
[myuser@myserver ~]$ sudo /etc/init.d/postfix stop
Stopping postfix : [ OK ]
[/CODE]
[CODE]
[zimbra@myserver ~]$ zmcontrol start
Host myserver.mydomain.fr
Starting zmconfigd…Done.
Starting logger…Done.
Starting convertd…Done.
Starting mailbox…Done.
Starting memcached…Done.
Starting proxy…Done.
Starting antispam…Done.
Starting antivirus…Done.
Starting opendkim…Done.
Starting snmp…Done.
Starting spell…Done.
Starting mta…Done.
Starting stats…Done.
[/CODE]
Now it looks like it should work better.
I have to check if mails are going in and out in the real world.

——

It’ all good !

Serveur de dépot local


Create Your Own Local Mirror of the Ubuntu Repositories
Category: Software / Tag: server, ubuntu / Add Comment

If you have several Ubuntu machines on a network, you might like to mirror the Ubuntu repositories locally so that you’re not wasting bandwidth downloading the same packages from the internet for every single machine. If you’ve already got an Ubuntu server up and running for some other task (such as ldap+kerberos+nfs type server, or a local web server) it’s very easy to add mirroring repository functionality to it. All you need is a spare ten minutes and ~35GB of free space for main, universe and multiverse and ~70GB if you also want the source packages (deb-src).

First step is to install apt-mirror:

sudo apt-get install apt-mirror

Now let’s edit the configuration file for apt-mirror:

sudo nano /etc/apt/mirror.list

The default configuration is as follows:

############# config ##################
#
# set base_path /var/spool/apt-mirror
#
# set mirror_path $base_path/mirror
# set skel_path $base_path/skel
# set var_path $base_path/var
# set cleanscript $var_path/clean.sh
# set defaultarch
# set postmirror_script $var_path/postmirror.sh
# set run_postmirror 0
set nthreads 20
set _tilde 0
#
############# end config ##############

deb http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu maverick-proposed main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu maverick-backports main restricted universe multiverse

deb-src http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
#deb-src http://archive.ubuntu.com/ubuntu maverick-proposed main restricted universe multiverse
#deb-src http://archive.ubuntu.com/ubuntu maverick-backports main restricted universe multiverse

clean http://archive.ubuntu.com/ubuntu

You can add extra repositories to the list, in the same format as the existing ones if you want to mirror these too. You can also change the path where you want the mirrored deb files to be stored. In my case I had a /spare partition set aside for future use and this is just perfect, so I’ve uncommented set base_path and changed /var/… to /spare. You may also like to remove the deb-src entries if you’re low on space unless you frequently use these to rebuild packages.

To specify the architecture that you want to mirror for use deb-i386 or deb-amd64 as the line prefix. You can also insert use a country code to specify that your mirror should be built from a mirror in your own country. This should make both your initial download and subsequent downloads much faster. To do this for the UK for example, use http://gb.archive.ubuntu.com/ubuntu

My final /etc/apt/mirror.list (which requires 52.0 GB of space) is as follows:

############# config ##################
#
set base_path /spare
#
# set mirror_path $base_path/mirror
# set skel_path $base_path/skel
# set var_path $base_path/var
# set cleanscript $var_path/clean.sh
# set defaultarch
# set postmirror_script $var_path/postmirror.sh
# set run_postmirror 0
set nthreads 20
set _tilde 0
#
############# end config ##############

deb-amd64 http://gb.archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-amd64 http://gb.archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-amd64 http://gb.archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
#deb http://gb.archive.ubuntu.com/ubuntu maverick-proposed main restricted universe multiverse
#deb http://gb.archive.ubuntu.com/ubuntu maverick-backports main restricted universe multiverse

deb-i386 http://gb.archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-i386 http://gb.archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-i386 http://gb.archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse

clean http://gb.archive.ubuntu.com/ubuntu

Having changed the base_directory, I need to create some directories under /spare like so:

sudo mkdir /spare/mirror
sudo mkdir /spare/skel
sudo mkdir /spare/var

Now we can perform our first manual update of the mirror by running the following:

sudo apt-mirror /etc/apt/mirror.list

If you’ve made a mistake with the config file and apt-mirror quits unexpectedly, you might find that the next time you run it you get the following:

apt-mirror is already running, exiting at /usr/bin/apt-mirror line 187.

If this is the case and you’re sure that apt-mirror is not running, then delete the lock file at /spare/var/apt-mirror.lock
Cron

In order to keep the mirror up-to-date automatically, we need to set up a cron job. Apt-mirror installs an example cron job at /etc/cron.d/apt-mirror:

#
# Regular cron jobs for the apt-mirror package
#
# 0 4 * * * apt-mirror /usr/bin/apt-mirror > /var/spool/apt-mirror/var/cron.log

If you remove the comment from the front of the last line, this will cause the mirror to be updated every day at 4am. If you want to change this you can read more about how cron jobs work here.
Apache – Configuring your mirror for http access

Ubuntu clients generally access repositories over http, we can set our mirror up for http access using apache2. If you’ve not already installed apache on your server, use:

sudo apt-get install apache2

Now we need to create a symbolic link from our repository mirror, to a directory served by apache:

sudo ln -s /spare/mirror/gb.archive.ubuntu.com/ubuntu/ /var/www/ubuntu

Clients

To get your clients to use the new mirror, simply update /etc/apt/sources.list with the new paths, for example:

# deb cdrom:[Ubuntu 10.10 _Maverick Meerkat_ – Release amd64 (20101007)]/ maverick main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://neo.danbishop.org/ubuntu/ maverick main restricted
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://neo.danbishop.org/ubuntu/ maverick-updates main restricted
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://neo.danbishop.org/ubuntu/ maverick universe
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick universe
deb http://neo.danbishop.org/ubuntu/ maverick-updates universe
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://neo.danbishop.org/ubuntu/ maverick multiverse
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick multiverse
deb http://neo.danbishop.org/ubuntu/ maverick-updates multiverse
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick-updates multiverse

## Uncomment the following two lines to add software from the ‘backports’
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://gb.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse
# deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical’s
## ‘partner’ repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu maverick partner
# deb-src http://archive.canonical.com/ubuntu maverick partner

## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
deb http://extras.ubuntu.com/ubuntu maverick main
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick multiverse
deb http://neo.danbishop.org/ubuntu/ maverick-updates multiverse
deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick-updates multiverse

## Uncomment the following two lines to add software from the ‘backports’
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://gb.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse
# deb-src http://gb.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical’s
## ‘partner’ repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu maverick partner
# deb-src http://archive.canonical.com/ubuntu maverick partner

## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
deb http://extras.ubuntu.com/ubuntu maverick main
deb-src http://extras.ubuntu.com/ubuntu maverick main

deb http://security.ubuntu.com/ubuntu maverick-security main restricted
deb-src http://security.ubuntu.com/ubuntu maverick-security main restricted
deb http://security.ubuntu.com/ubuntu maverick-security universe
deb-src http://security.ubuntu.com/ubuntu maverick-security universe
deb http://security.ubuntu.com/ubuntu maverick-security multiverse
#deb http://gb.archive.ubuntu.com/ubuntu/ maverick-proposed restricted main multiverse universe
deb-src http://security.ubuntu.com/ubuntu maverick-security multiverse

LVM : Renommer un groupe de volumes


Sites sur LVM :
http://www.ibiblio.org/pub/Linux/docs/HOWTO/LVM-HOWTO
http://wiki.deimos.fr/LVM_:_Utilisation_des_LVM

Renommer un groupe de volumes



lvmVous est-il déjà arrivé de devoir connecter à votre machine un disque externe sur lequel un groupe de volumes porte le même nom que celui que vous utilisez ?

Pas de panique, il y a une solution.

La commande vgscan nous liste les groupes de volumes disponibles :
Source code

# vgscan

Reading all physical volumes. This may take a while…
WARNING: Duplicate VG name vg_starfury: cBZ2cQ-ujXP-zA31-ao1E-n38k-km5B-N1ARaJ
(created here) takes precedence over h09gYp-JRIE-xkt7-g9mV-fc5S-fo47-fWj8O1
Found volume group « vg_starfury » using metadata type lvm2
Found volume group « vg_starfury » using metadata type lvm2

On peut constater que si les noms de groupes de volumes sont identiques, il reste l’Universal Unique IDentifier pour les différencier. De plus, la commande vgscan nous indique l’UUID du groupe de volumes utilisé par le système et de celui qu’il faudra renommer.

Nous allons maintenant utiliser la commande vgrename qui va nous permettre de renommer le groupe de volumes du disque externe afin qu’il soit accessible et utilisable sur notre machine.
Source code

# vgrename h09gYp-JRIE-xkt7-g9mV-fc5S-fo47-fWj8O1 vg_old_starfury

WARNING: Duplicate VG name vg_starfury: cBZ2cQ-ujXP-zA31-ao1E-n38k-km5B-N1ARaJ
(created here) takes precedence over h09gYp-JRIE-xkt7-g9mV-fc5S-fo47-fWj8O1
WARNING: Duplicate VG name vg_starfury: Existing cBZ2cQ-ujXP-zA31-ao1E-n38k-km5B-N1ARaJ
(created here) takes precedence over h09gYp-JRIE-xkt7-g9mV-fc5S-fo47-fWj8O1
WARNING: Duplicate VG name vg_starfury: cBZ2cQ-ujXP-zA31-ao1E-n38k-km5B-N1ARaJ
(created here) takes precedence over h09gYp-JRIE-xkt7-g9mV-fc5S-fo47-fWj8O1
Volume group « vg_starfury » successfully renamed to « vg_old_starfury »

Un nouveau vgscan nous permet de vérifier que l’opération s’est bien effectuée.
Source code

# vgscan

Reading all physical volumes. This may take a while…
Found volume group « vg_starfury » using metadata type lvm2
Found volume group « vg_old_starfury » using metadata type lvm2

GNU/Linux lvm

Serveur IRC


Solution unrealIRC
sudo apt-get install build-essential
wget http://www.unrealircd.com/downloads/Unreal3.2.10.1.tar.gz
  1. gunzip -d Unreal3.2.X.tar.gz
  2. tar xvf Unreal3.2.X.tar
  3. cd Unreal3.2
==[ COMPILING ]==
To build the ircd, run:
./Config
Answer these questions to the best of your knowledge. 
Generally if your not sure, the default will work just fine!
make

If you specified an alternative location during ./Config you also need
to run "make install".

==[ MAKING A CONFIG FILE ]==
If you are new, then you need to create your own configfile:

copy doc/example.conf to your main UnrealIRCd directory and call
it unrealircd.conf .
Then open it in an editor and carefully modify it, consult the docs
(doc/unreal32docs.html, or online: www.unrealircd.com/unreal32docs.html)
for more information about every block/setting.
Common problems are explained in the FAQ, which is located at:
http://www.vulnscan.org/UnrealIrcd/faq/ .

==[ BOOTING YOUR IRCD ]==
Just type: ./unreal start
Note that after booting the errors are usually logged to ircd.log,
so check that file if you have any problems.
Again, check the FAQ (and docs) if you have any boot problems.
http://www.unrealircd.com
http://www.vulnscan.org/UnrealIRCd/unreal32docs.html#installation

 

 

Solution ircd-hybrid + ZNC + hybserv

Howto setup the Ultimate IRC Server
September 23, 2012 by Christopher Sexton

While I like Campfire and HipChat and those other tools for group collaboration there is just something nice about using an IRC channel. Probably the most compelling reason is that I am going to have my IRC client running anyway for other channels — so it would be nice to just add a server and use the same client I am already using.

At Radius we had been using a public server for a little bit of communication, but the converstaions starting becoming more technical and wasn’t happy having things go through someone else’s server, and be unencrypted. So I decided to setup my own. I give you the ultimate irc setup:
The Ultimate IRC Server

The ultimate server consists of a few components:

The IRC server itself (ircd-hybrid)
an IRC bouncer (ZNC)
a way to tunnel port 443 to the bouncer
and maybe a bot that can post funny pictures of cats for you

I am using Ubuntu Server 12.04.1 LTS (ami-137bcf7a) running on a micro instance.
Install the IRC Server

sudo apt-get install ircd-hybrid
sudo vim /etc/ircd-hybrid/ircd.motd

Create the password required to be the Oper:

WARNING: Please do not mix up the mkpasswd program from /usr/sbin with this one. If you are root, typing mkpasswd will run that one instead and you will receive a strange error.

/usr/bin/mkpasswd super-secret

Edit the config file, this is well documented and there are plenty of little tweaks you can make but make a couple little changes now:

sudo vim /etc/ircd-hybrid/ircd.conf

Comment out the host parameter in the listen section (about line 130 in the default ubuntu config)

host = “127.0.0.1″;

to be

#host = “127.0.0.1″;

And increase the max_clients in the serverinfo section:

max_clients = 2;

to be

max_clients = 512;

This will open the server up to external connections (Note: make sure you configure your instance to have these ports open, e.g. in EC2 you will need to edit the security profile and open ports 443, 6664, and 6667), and allow more than 2 folks to connect from the same IP (which is important since we will have everyone connect via ZNC running on this machine).

Now restart the server

sudo /etc/init.d/ircd-hybrid restart

Now you should be able to fire up your favorite client and see if you can get it to connect to the server. Once you have proven it works, time to move onto the bouncer.
Install the IRC Bouncer

Originally I followed the guide from Dustin Davis but have a few tweaks:

sudo apt-get install znc
znc –makeconf

Follow the guides to setup the server. I mostly choose the defaults, and enabled all the modules

What port would you like ZNC to listen on? (1025 to 65535): 6664
Would you like ZNC to listen using SSL? (yes/no) [no]: yes
Would you like to create a new pem file now? (yes/no) [yes]: yes
Listen Host (Blank for all ips):
Number of lines to buffer per channel [50]: 1000
Would you like to keep buffers after replay? (yes/no) [no]: yes

Configure ZNC to use the brand new IRC server that we just installed:

IRC server (host only): 127.0.0.1
[127.0.0.1] Port (1 to 65535) [6667]: 6667
[127.0.0.1] Password (probably empty):
Does this server use SSL? (yes/no) [no]:
Would you like to add another server for this IRC network? (yes/no) [no]: no
Would you like to add a channel for ZNC to automatically join? (yes/no) [yes]: yes
Would you like to add another channel? (yes/no) [no]: no
Would you like to set up another user (e.g. for connecting to another network)? (yes/no) [no]: no
Launch ZNC now? (yes/no) [yes]: no

Now you can run ZNC as that user and verify it works, and make tweaks to the config.

vi .znc/configs/znc.conf

or with the webadmin module by pointing a browser to

https://yourhostname:6664

To verify that this works with your local client you should just have to change the port from 6667 to 6664. If you want to compare settings my initial config file looked something like this.
Make ZNC a system daemon

At the end of the config keep it running and connect to it from your local IRC client to make sure things are working. Once you have proven it works time to set it up as a daemon that starts at boot. I used Henner’s guide when I first set this up.

killall znc # just to make sure

Create the user and group

sudo addgroup –system znc
sudo adduser –system –no-create-home –ingroup znc znc

Create the init script, I have the one I use up here

sudo vim /etc/init.d/znc

It’s pretty big, so you may want to curl it down

curl https://raw.github.com/gist/3772971/efbe88004be70cb7f157e30aa1183ea5867d8de6 > /etc/init.d/znc

Copy over the ZNC config files to /etc, and update permissions

sudo mkdir /etc/znc
sudo mv /home/$USER/.znc/* /etc/znc/
rm -R /home/$USER/.znc
chown -R znc:znc /etc/znc
sudo chown -R znc:znc /etc/znc
sudo chmod +x /etc/init.d/znc

Start ‘er up

sudo /etc/init.d/znc start

Setup port forwarding

Forward from 443 to 6664 to work around firewalls.

This step is not required if your network does not block the ports we are using. But it is still nice to use in case you ever find yourself on one. Also you would not want to do this on a server that is serving webpages over https.

sudo apt-get install rinetd
sudo vim /etc/rinetd.conf

Edit that file to include a new forwarding rule

0.0.0.0 443 127.0.0.1 6664

Restart rinetd

sudo /etc/init.d/rinetd restart

If you enabled the webadmin module in ZNC you should now be able to point your browser to https://yourhostname and edit your ZNC config (and let folks edit their accounts, configure modules and change passwords). Yes, ZNC uses the same port for IRC connections and for the admin page.
Recap

Now you should have an irc server running on port 6667, a bouncer running on port 6664, and a tunnel for the bouncer from port 443.

I just used the web admin module to setup accounts for everyone on my team. I wound up turning off external access to 6667 so that I didn’t have to secure ircd, and everyone just goes through ZNC.

You might want to setup an bot to do your bidding, I use radbot. You should fork 🙂

http://www.codeography.com/2012/09/23/howto-irc-server.html
http://eosrei.net/articles/2013/03/irc-server-ircd-hybrid-and-hybserv-ubuntu-1204lts
http://www.gila.org/blog/2010/06/connecting-ircd-hybrid-to-hybserv
http://mea-poulpa.blogspot.fr/2010/04/montez-votre-propre-serveur-de-tchat.html
https://github.com/dkorunic/hybserv2

resolvconf


Le fichier « resolv.conf » permet d’indiquer le ou les domaines de recherche et les différents serveurs DNS à utiliser.

Ainsi, lorsqu’un client recherche une adresse en dehors du nom de domaine local (google.fr par exemple), dnsmasq (l’application que nous allons utiliser pour les services de DHCP et de DNS) va interroger les serveurs listés dans resolv.conf. Dnsmasq va alors garder le résultat dans un cache pour les requêtes futures

Par exemple, dans un réseau local, nous pourrions avoir un serveur DNS à l’adresse 192.168.1.2 chargé de gérer le domaine « exemple.fr ». En cas de défaillance du DNS local, nous pourrions faire appel aux serveurs DNS de Google (ou du fournisseur d’accès). Dans ce cas, le contenu du fichier « /etc/resolv.conf », pourrait ressembler à cela :

nameserver 192.168.1.2
nameserver 8.8.8.8
nameserver 8.8.4.4
search exemple.fr

La première ligne indique l’adresse du serveur DNS du réseau local. En cas de défaillance de ce serveur, les serveurs suivants seront utilisés.

La dernière ligne permet d’indiquer le nom du domaine géré par le serveur DNS local. Par exemple, si nous cherchons à contacter le serveur « MonServeur », le système cherchera en fait à contacter l’adresse complète « MonServeur.exemple.fr », car le nom du serveur indiqué ne comportait pas le domaine de recherche.

Présentation et installation de resolvconf


Le paquet « resolvconf » permet de gérer très finement le contenu du fichier « /etc/resolv.conf » servant à la résolution des noms en fonction du type de connexion utilisé et en récupérant les informations à différents endroits statiques ou dynamiques (clients ppp, dhcp ou autres).

 

sudo aptitude install resolvconf

Sur ma machine, le paquet était déjà installé.

Une fois le paquet « resolvconf » installé, il ne faut plus modifier le fichier « /etc/resolv.conf », car le contenu de celui-ci sera automatiquement géré et remplacé par « resolvconf ».

Utilisation de resolvconf avec une interface de type « eth0 »


Le configuration de ce type d’interface est faite dans le fichier « /etc/network/interfaces ».

Par exemple, pour une interface de type « eth0 », il faut ajouter les lignes « dns-nameservers » et « dns-search » au contenu du fichier « /etc/network/interfaces ». Exemple

iface eth0 inet dhcp
dns-nameservers 192.168.1.2 8.8.8.8 8.8.4.4
dns-search exemple.fr

Pour vérifier que tout fonctionne correctement, il faut commencer par désactiver l’interface « eth0 » :

sudo ifdown eth0

Après cette commande, le fichier « /etc/resolv.conf » doit être vidé et devrait donc ressembler à cela :

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND — YOUR CHANGES WILL BE OVERWRITTEN

Et après l’activation de l’interface « eth0 » :

sudo ifup eth0

Le fichier « /etc/resolv.conf » devrait ressembler à cela :

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND — YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.2
nameserver 8.8.8.8
nameserver 8.8.4.4
search exemple.fr

Remarque : Il est possible de personnaliser le message d’avertissement des deux premières lignes (pour le mettre par exemple en français) en modifiant le contenu du fichier « /etc/resolvconf/resolv.conf.d/head »

Scribus, un PAO


http://doc.ubuntu-fr.org/scribus

 

http://wiki.scribus.net/canvas/Prise_en_main_de_Scribus

http://wiki.scribus.net/canvas/Get_Started_with_Scribus

 

Imprimer au format livre :

http://wiki.scribus.net/canvas/How_to_make_a_booklet

Method A-1: using psutils only


1) Change the document format to postscript:
pdf2ps file.pdf

This creates a postscript file named ‘file.ps’

2) Change the order of the pages:
psbook -s16 file.ps fileA.ps

Where 16 is the number of pages that your document has. It should be a multiple of four.

3) Arrange the pages so two logical pages are printed on one physical sheet:
psnup -2 -w21cm -h16.3cm -W10.5cm -H16.3cm fileA.ps fileB.ps

Which arranges two logical pages of the size 105x163mm on a sheet of the size 210x163mm. If you have different page sizes, then simply change the dimensions. (Take a look to the man page of psnup) You can alternatively use the -p and -P flags to indicate page sizes:
psnup -2 -pa4 -Pa5 fileA.ps fileB.ps

which will take two A5 pages and put them on A4 paper.

4) Transform it back to pdf:
ps2pdf fileB.ps

This creates the file ‘fileB.pdf’.

5) Print ‘fileB.pdf’ with the program of your choice.

Logiciel de contrôle à distance


Quels logiciels peuvent permettre de prendre la main à distance sur une autre machine à travers internet ?
Dans l’idéal, ce serait une application rapide à lancer, pré-configurée.
Deux types :