This app provides monitoring and information features for the common freifunk user and the technical stuff of a freifunk community. Code base is taken from a TUM Practical Course project and added here to see if Freifunk Altdorf can use it. https://www.freifunk-altdorf.de
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Bernhard Blieninger fc05486403 initial commit taken from gitlab.lrz.de 6 years ago
..
CHANGELOG.md initial commit taken from gitlab.lrz.de 6 years ago
LICENSE.txt initial commit taken from gitlab.lrz.de 6 years ago
README.md initial commit taken from gitlab.lrz.de 6 years ago
index.js initial commit taken from gitlab.lrz.de 6 years ago
package.json initial commit taken from gitlab.lrz.de 6 years ago
signals.js initial commit taken from gitlab.lrz.de 6 years ago

README.md

signal-exit

Build Status Coverage NPM version Windows Tests Standard Version

When you want to fire an event no matter how a process exits:

  • reaching the end of execution.
  • explicitly having process.exit(code) called.
  • having process.kill(pid, sig) called.
  • receiving a fatal signal from outside the process

Use signal-exit.

var onExit = require('signal-exit')

onExit(function (code, signal) {
  console.log('process exited!')
})

API

var remove = onExit(function (code, signal) {}, options)

The return value of the function is a function that will remove the handler.

Note that the function only fires for signals if the signal would cause the proces to exit. That is, there are no other listeners, and it is a fatal signal.

Options

  • alwaysLast: Run this handler after any other signal or exit handlers. This causes process.emit to be monkeypatched.