Sur le budget 2018, avec 100 € que l’État perçoit sur mes revenus, je finance :
13€ Développement des territoires 25€ Education et recherche 1€ Culture, sports et loisirs 11€ Solidarité 5€ Union européenne 11€ Charge de la dette 2€ Vie citoyenne 2€ Transition écologique 20€ Défense et sécurité 1€ Transports 4€ Logement et politique de la ville 5€ Soutien à l’économie
-> 20% à la défense...

Pas plus simple :
I think I have a simpler solution here, just look for a directoy whose name corresponds to the PID you are looking for, under the pseudo-filesystem accessible under the /proc path. So if you have a program running, whose ID is 1199, cd into it:
$ cd /proc/1199

Then look for the fd directory underneath

$ cd fd

This fd directory hold the file-descriptors objects that your program is using (0: stdin, 1: stdout, 2: stderr) and just tail -f the one you need - in this case, stdout):

$ tail -f 1

personnellement j'aime beaucoup mate mais avec si peu de RAM évite les environnements lourds, GNOME and co, KDE. le reste devrait tourner. évite aussi evolution, très gourmand.

et jamais honte !

Une surprise ? j'ai trois personnes dans ma famille proche qui ont des effets indésirables suite au changement de formule...

manger liquide, manger rapide.

Hey Reg,
I am far from an expert on Zabbix but have a couple of suggestions.
One approach would be to use a performance counter in the “SQL ServerBigGrinatabase Mirroring” group as an indicator. You could try the size of the Log Send Queue to see if it grows too high, or maybe the Transaction delay time. Advantage, built-in counter, disadvantage, difficult to correlate with mirror status you want.
Another approach would be to utilize one of the performance counters in the “SQL Server :User Settable” category. You would have to use sp_user_counter to set the value. This could be done with a scheduled job. You could query the mirror/AlwaysOn status and set the value to a flag you would use as the health indicator for Zabbix. For example 0 for mirror/AlwaysOn status OK, 1 or greater for a problem. Advantage, uses ability of Zabbix to leverage the the perf counter infrastructure, disadvantage, relies on SQL job to update value and uses one out of only 10 available user defined counters.
Example Mirroring query:

SELECT count (*)
FROM sys.database_mirroring
WHERE mirroring_role_desc IN ('PRINCIPAL','MIRROR')
AND mirroring_state_desc NOT IN ('SYNCHRONIZED','SYNCHRONIZING');

Example AlwaysOn Query:

-- 0 is good, any number greater than 0 is bad
SELECT COUNT (*) FROM [master].[sys].[dm_hadr_database_replica_states]
WHERE [synchronization_health_desc] != N'HEALTHY' ;

A third approach would be to embed a T-SQL query in the Zabbix agent configuration file that would set a value that would correspond to an Item in Zabbix. Similar to the User Settable approach but uses the Zabbix agent to refresh the value of the Zabbix Item instead of a SQL job to set the built in performance counter. Advantage, leverages Zabbix functionality, does not need separate SQL job, disadvantage, need to embed SQL connection into Zabbix.
https://msdn.microsoft.com/en-us/library/ms187480.aspx
https://www.zabbix.com/forum/showthread.php?t=44517&page=2
https://www.zabbix.com/forum/showthread.php?t=15865
[http://serverfault.com/questions/275517/zabbix-populate-item-with-sql-server-query
http://serverfault.com/questions/512521/zabbix-monitoring-custom-values
http://serverfault.com/questions/128090/how-to-query-custom-performance-counters-using-zabbix-agent

"899,99 euros au lieu d'au moins 900 euros." -> ha oui, sacrée reduc :-)

Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU

sudo wget http://pastebin.com/raw.php?i=p3QyuXzZ -O /usr/share/mibs/ietf/SNMPv2-PDU

Oui, pour rappel, dans certains cas, et même assez souvent, un danger de vie ou de mort nous fige.

Comment l'Europe trouve une solution facile, peu coûteuse, pour plusieurs dizaines de pays.

"PS/2 Mouse support improvements" -> sérieux ???

Bon, encore un rapport que certains nieront...

XD

beurk....

@winfinder really great new !

bien d'accord avec toi, mais le problème reste le même avec un framagit : la centralisation des services les rend dépendant de leur plateforme d'hébergement. La solution serait soit un système réparti (fédérations) ou au minimum un système de miroirs comme le font les repos Linux, etc.

Problem
ssh root@192.168.2.203
Unable to negotiate with 192.168.2.203 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1
Solution
ssh root@192.168.2.203 -oKexAlgorithms=+diffie-hellman-group1-sha1
Ou ssh -c cyphername root@192.168.2.203

"cat /dev/null > ~/.bash_history && history -c && exit"

et merde...