return {
on = timer = {
function(domoticz)
-- use domoticz.variables(..) here and return true when the timer should go off
end
},
execute = function(domoticz, timer, triggerInfo)
end
}
Merci pour ce lien ! ( via https://shaar.libox.fr/?oEo7eA )
c'est vraiment facile d'apprendre les différents outils avec cette page ;)
Setting Up New Permissions
The new permissions structure is simple. Instead of creating a new permission GRANT for every database, we are just going to GRANT the user basic access to the namespace. MySQL has two wildcard characters: and %. If you need them to be interpreted literally, just escape them with . The following command will grant the necessary permissions to the MySQL user to access and update all the databases in the phabricator namespace.
GRANT SELECT, INSERT, UPDATE, DELETE, EXECUTE, SHOW VIEW ON `phabricator\_%`.* TO 'phabric'@'localhost';
Great, now whenever a new Phabricator upgrade comes along that changes the database structure, there shouldn't be much that needs to be done in terms of granting and deleting permissions.
Cela explique pourquoi je suis toujours sur PHP ou .net core, ou Java, ou...(remplacer par vrai langage)
et que j’aime toujours autant les moteurs de template
et pourquoi je ne comprends pas les sites avec 25JS pour afficher du HTML simple, sans formulaires, sans carroussels, etc.
bref… je suis un vieux… devenu Architecte et mon boulot :
« et j’aimerai faire cela, regarde c’est trop cool, bla bla bla
Moi: c’est bien mais “bla bla bla” c’est déjà géré par l’application X et celle-ci gère en plus …
Eux: ah oui, mais on est en 2018, l’application X elle est trop moche »
…
If Xcompmgr is used solely to provide tint2 with transparency effects it can be run at boot by changing the autostart section in ~/.config/openbox/autostart to this:
if which tint2 >/dev/null 2>&1; then
(sleep 2 && xcompmgr) &
(sleep 2 && tint2) &
fi
Other (better) ways to make Xcompmgr run at startup are discussed in the Openbox article.
Fullscreen/Overlay
To force tint2 to stay on top of the application (overlay), you need to set the panel_layer option appropriately. This can be helpful when you switch from a fullscreen window to a normal application using Alt-Tab. There is a discussion on this at Crunchbang Forum
#Panel
panel_layer = top
strut_policy = follow_size
Tint2 se présente sous forme d'une barre de tâches très légère et facile à configurer.
Il inclut une zone de notification (systray).
Son installation et sa configuration sont faciles à réaliser en éditant son fichier “tint2rc”.
Cependant, un utilitaire graphique permet de le faire tintwizard.
Donc en gros sous débian :
format aaaa-mm-jj
echo %date:~6,4%-%date:~3,2%-%date:~0,2%
Bonjour,
J'ai installé mon serveur en débian9, celui-ci utilise domoticz et un rflink pour gérer ma domotique...
depuis l'installation j'avais des pertes d'informations...
j'ai d'abord pensé aux piles de mes sondes.... mais non...
c'était le serveur
et oui après un certains temps le port USB est mis en "basse consommation" par linux et donc moins de puissances pour la réception / envoi d'information.
donc j'ai ajouté une rêgle dans UDEV:
SUBSYSTEM=="usb", ATTR{idProduct}=="7523", ATTR{idVendor}=="1a86", SYMLINK+="rflink", TEST=="power/control" ATTR{power/control}="on"
The user interface for dynamic PM
The user interface for controlling dynamic PM is located in the power/ subdirectory of each USB device’s sysfs directory, that is, in /sys/bus/usb/devices/.../power/ where ”...” is the device’s ID. The relevant attribute files are: wakeup, control, and autosuspend_delay_ms. (There may also be a file named level; this file was deprecated as of the 2.6.35 kernel and replaced by the control file. In 2.6.38 the autosuspend file will be deprecated and replaced by the autosuspend_delay_ms file. The only difference is that the newer file expresses the delay in milliseconds whereas the older file uses seconds. Confusingly, both files are present in 2.6.37 but only autosuspend works.)
power/wakeup
This file is empty if the device does not support remote wakeup. Otherwise the file contains either the word enabled or the word disabled, and you can write those words to the file. The setting determines whether or not remote wakeup will be enabled when the device is next suspended. (If the setting is changed while the device is suspended, the change won’t take effect until the following suspend.)
power/control
This file contains one of two words: on or auto. You can write those words to the file to change the device’s setting.
on means that the device should be resumed and autosuspend is not allowed. (Of course, system suspends are still allowed.)
auto is the normal state in which the kernel is allowed to autosuspend and autoresume the device.
(In kernels up to 2.6.32, you could also specify suspend, meaning that the device should remain suspended and autoresume was not allowed. This setting is no longer supported.)
power/autosuspend_delay_ms
This file contains an integer value, which is the number of milliseconds the device should remain idle before the kernel will autosuspend it (the idle-delay time). The default is 2000. 0 means to autosuspend as soon as the device becomes idle, and negative values mean never to autosuspend. You can write a number to the file to change the autosuspend idle-delay time./domoticz/domoticz: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
In stretch, libssl is at version 1.1.0.
Solution for me (64bit Debian Stretch):
1) Download https://packages.debian.org/jessie/amd64/libssl1.0.0/download
2) dpkg -i libssl1.0.0*
Partitioning Scheme for SSD
Better leave all read-only files on SSD and use hard disk for everything else
https://wiki.debian.org/ReadonlyRoot should clarify which parts of the filesystem tree can be read-only: moving /usr to read-only would be the most significant thing (greatest space required) I guess but you have to ensure it is remounted as required when doing apt-get install or remove. See that page for more info.Solid (derived from "social linked data") is a proposed set of conventions and tools for building decentralized social applications based on Linked Data principles. Solid is modular and extensible and it relies as much as possible on existing W3C standards and protocols.
xoreos is an open source implementation of Bioware's Aurora engine and its derivatives, licensed under the terms of the GNU General Public License version 3 (or later).
In order to accurately reimplement these games, we need to research how all of the mechanics work. If you feel like crawling deep into the bowels of the Aurora engine, or have already done so, please feel free to document your newly gained understandings here.