I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

I Received a 2012 O’Reilly Open Source Award

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/07/23/award.html

On last Friday 20 July
2012, I
received

an O’Reilly
Open Source Award
, in appreciation for my decade of work in Free
Software non-profit organizations, including my current daily work at
the Software Freedom Conservancy, my work at the

FSF (including
starting FSF’s associate membership program), and for my work creating
and defending copyleft licensing, including such things as inventing the
idea behind
the Affero
clause
, helping
draft AGPLv3,
and, more generally, enforcing copyleft.

I’m very proud of all this work. My obsession with software freedom
goes back far into my past, when I downloaded my first copy
of GNU Emacs in 1991
from Usenet and my first GNU/Linux
distribution, SLS,
in 1992, booting for the first time, on the first computer I ever
owned, a copy of Linux 0.99pl12.

I honestly have written a lot less Free Software than I wanted to.
I’ve made a patch here and there over the years to dozens of projects.
I was a co-maintainer of the AGPL’d
PokerSource system
for a while, and I made various (mostly
mixed-success) attempts to build a
better virtual machine for Perl
, which now is done much
better than I ever
did
by the Parrot project.

Despite the fact that making better software was what enthralled me
most, feeling the helplessness of supporting, using and writing
proprietary software in my brief for-profit career convinced me that lack
of adequate software freedom was the most dangerous social justice problem
in the computing community. I furthermore realized that lots of people
were ready and willing to write great Free Software, but that few wanted
to do the (frankly more boring) work of running non-profit organizations
to defend and advance software freedom. Thus, I devoted myself to helping
FSF and Conservancy to be successful organizations that could assist in
that regard. I’m privileged and proud to continue my service to both of
these organizations.

Being recognized for this work means a great deal to me. Awards have a
special meaning for me, because financial success never really mattered
much to me, but knowing that I’ve made a contribution to something
greater than myself matters greatly. Receiving an award that indicates
that I’ve succeeded in that regard invigorates me to do even more. So,
at this moment of receiving this award, I’d like to thank all of you in
the software freedom community who appreciate
and support my work. It
means a great deal to me that my work has made a positive impact.

Upcoming Hackfests/Sprints

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/hackfests.html

The Linux Plumbers
Conference 2012
will take place August 29th to 31st in San Diego,
California. We, the systemd
developers, would like to invite you to two hackfests/sprints that will happen
around LPC:

San Diego: libvirt/LXC/systemd/SELinux Integration Hackfest

On 28th of August we’ll have a hackfest on the topic of closer
integration of libvirt, LXC, systemd and SELinux, colocated with LPC in
San Diego, California. We’ll have a number of key people from these projects
participating, including Dan Walsh, Eric Paris, Daniel P. Berrange, Kay
Sievers and myself.

Topics we’ll cover: making Fedora/Linux boot entirely cleanly in
normal containers, teaching systemd’s control tools minimal
container-awareness (such as being able to list all services of all
containers in one go, in addition to those running on the host
system), unified journal logging across multiple containers, the systemd
container interface
, auditing and containers, running multiple
instances from the same /usr tree, and a lot more…

Who should attend? Everybody hacking on the mentioned
projects who wants to help integrating them with the
goal of turning them into a secure, reliable, powerful container
solution for Linux.

Who should not attend? If you don’t hack on any of these
projects, or if you are not interested in closer integration of at
least two of these projects.

How to register? Just show up. You get extra points however
for letting us know in advance (just send us an email). Attendance is
free.

➥ See also: Google+ Event

San Francisco: systemd Journal Sprint

On September 3-7 we’ll have a sprint on the topic of the systemd
Journal. It’s going to take place at the Pantheon headquarters in San
Francisco, California. Among others, Kay Sievers, David Strauss and I will participate.

Who should attend? Everybody who wants to help improving the
systemd Journal, regardless if in its core itself, in client software
for it, hooking up other projects or writing library bindings for
it. Also, if you are using or planning to use the journal for a
project, we’d be very interested in high-bandwith face-to-face
feedback regarding what you are missing, what you don’t like so much, and what
you find awesome in the Journal.

How to register? Please sign up at EventBrite. Attendance is
free. For more information see the invitation
mail
.

➥ See also: Google+ Event

See you in California!

WinConn

Post Syndicated from RealEnder original https://alex.stanev.org/blog/?p=302

От години използвам Linux като основна работна среда.

От горното изречение, особено думата “основна”, личи, че понякога се налага и да се пали win/mac, където се стартират ред приложения, било поради недобра съвместимост, било защото просто са специализиран софтуер, писан само за конкретната операционна система.

Години наред решението бе да се закачиш на отдалечена машина по VNC/RDP/whatever и да си свършиш работата по най-бързия начин, преди да си се издразнил от разликите в интерфейса и от това да падне продуктивността. Възможностите за seamless интеграция (използване на отдалечените приложения въвместно с останалите в работната среда) бяха ограничени и трудни за конфигуриране и използване – SeamlessRDP на rdesktop, Seamless mode на VirtualBox, VMware Fusion и т.н.

Благодарение на развитието на проекта FreeRDP, вече имаме свободна имплементация на RemoteApp. Липсващото парченце от пъзела е приложение, което да улесни конфигурирането на отдалечените приложения.

За целта последните дни работих върху WinConn, графичен мениджър за RemoteApp приложения с отворен код. На страницата можете да видите задължителните снимки на екрана, видео в действие и да го инсталирате от моето PPA в Ubuntu.

Разработката на WinConn съвпадна с Ubuntu App Showdown – триседмичен конкурс за програмиране на приложения в Ubuntu. Ако ви хареса, след 10ти юли ще можете да гласувате чрез рейтинговата система в Ubuntu Software Centre. Разбира се, приемам всякакви предложения за подобрения, бъгове и т.н. в Launchpad.

Изгрев

Post Syndicated from RealEnder original https://alex.stanev.org/blog/?p=296

Та след близо година затишие, реших да подновя графоманските напъни в блога.

Вероятно вече не останаха приятели и познати, които не знаят за промяната в кариерното ми развитие, но за пълнота ще добавя, че в момента работя в Synapse Ideas. Правим активно това, от което разбираме най-добре – електронни услуги, специализирани софтуерни решения, отворен код и т.н., но без тежкия overhead на голямата организация. По пътя към главната ни цел (world domination, разбира се) работим и върху други, доста интересни проекти, за които ще пиша когато му дойде времето(tm).

Междувременно Информационно обслужване АД премина през сериозни трансформации – нов управлениски екип, (най-после) опит за дефиниране на управленска визия и т.н. Аз лично вярвам, че е за добро и пожелавам успех на колегите.

На финала да перефразирам: България е малка и въпреки това, спасение дебне отвсякъде 🙂

systemd for Administrators, Part XV

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/watchdog.html

Quickly
following the previous iteration
, here’s
now the fifteenth
installment
of

my ongoing series
on
systemd
for
Administrators:

Watchdogs

There are three big target audiences we try to cover with systemd:
the embedded/mobile folks, the desktop people and the server
folks. While the systems used by embedded/mobile tend to be
underpowered and have few resources are available, desktops tend to be
much more powerful machines — but still much less resourceful than
servers. Nonetheless there are surprisingly many features that matter
to both extremes of this axis (embedded and servers), but not the
center (desktops). On of them is support for watchdogs in
hardware and software.

Embedded devices frequently rely on watchdog hardware that resets
it automatically if software stops responding (more specifically,
stops signalling the hardware in fixed intervals that it is still
alive). This is required to increase reliability and make sure that
regardless what happens the best is attempted to get the system
working again. Functionality like this makes little sense on the
desktop[1]. However, on
high-availability servers watchdogs are frequently used, again.

Starting with version 183 systemd provides full support for
hardware watchdogs (as exposed in /dev/watchdog to
userspace), as well as supervisor (software) watchdog support for
invidual system services. The basic idea is the following: if enabled,
systemd will regularly ping the watchdog hardware. If systemd or the
kernel hang this ping will not happen anymore and the hardware will
automatically reset the system. This way systemd and the kernel are
protected from boundless hangs — by the hardware. To make the chain
complete, systemd then exposes a software watchdog interface for
individual services so that they can also be restarted (or some other
action taken) if they begin to hang. This software watchdog logic can
be configured individually for each service in the ping frequency and
the action to take. Putting both parts together (i.e. hardware
watchdogs supervising systemd and the kernel, as well as systemd
supervising all other services) we have a reliable way to watchdog
every single component of the system.

To make use of the hardware watchdog it is sufficient to set the
RuntimeWatchdogSec= option in
/etc/systemd/system.conf. It defaults to 0 (i.e. no hardware
watchdog use). Set it to a value like 20s and the watchdog is
enabled. After 20s of no keep-alive pings the hardware will reset
itself. Note that systemd will send a ping to the hardware at half the
specified interval, i.e. every 10s. And that’s already all there is to
it. By enabling this single, simple option you have turned on
supervision by the hardware of systemd and the kernel beneath
it.[2]

Note that the hardware watchdog device (/dev/watchdog) is
single-user only. That means that you can either enable this
functionality in systemd, or use a separate external watchdog daemon,
such as the aptly named watchdog.

ShutdownWatchdogSec= is another option that can be
configured in /etc/systemd/system.conf. It controls the
watchdog interval to use during reboots. It defaults to 10min, and
adds extra reliability to the system reboot logic: if a clean reboot
is not possible and shutdown hangs, we rely on the watchdog hardware
to reset the system abruptly, as extra safety net.

So much about the hardware watchdog logic. These two options are
really everything that is necessary to make use of the hardware
watchdogs. Now, let’s have a look how to add watchdog logic to
individual services.

First of all, to make software watchdog-supervisable it needs to be
patched to send out “I am alive” signals in regular intervals in its
event loop. Patching this is relatively easy. First, a daemon needs to
read the WATCHDOG_USEC= environment variable. If it is set,
it will contain the watchdog interval in usec formatted as ASCII text
string, as it is configured for the service. The daemon should then
issue sd_notify("WATCHDOG=1")
calls every half of that interval. A daemon patched this way should
transparently support watchdog functionality by checking whether the
environment variable is set and honouring the value it is set to.

To enable the software watchdog logic for a service (which has been
patched to support the logic pointed out above) it is sufficient to
set the WatchdogSec= to the desired failure latency. See systemd.service(5)
for details on this setting. This causes WATCHDOG_USEC= to be
set for the service’s processes and will cause the service to enter a
failure state as soon as no keep-alive ping is received within the
configured interval.

If a service enters a failure state as soon as the watchdog logic
detects a hang, then this is hardly sufficient to build a reliable
system. The next step is to configure whether the service shall be
restarted and how often, and what to do if it then still fails. To
enable automatic service restarts on failure set
Restart=on-failure for the service. To configure how many
times a service shall be attempted to be restarted use the combination
of StartLimitBurst= and StartLimitInterval= which
allow you to configure how often a service may restart within a time
interval. If that limit is reached, a special action can be
taken. This action is configured with StartLimitAction=. The
default is a none, i.e. that no further action is taken and
the service simply remains in the failure state without any further
attempted restarts. The other three possible values are
reboot, reboot-force and
reboot-immediate. reboot attempts a clean reboot,
going through the usual, clean shutdown logic. reboot-force
is more abrupt: it will not actually try to cleanly shutdown any
services, but immediately kills all remaining services and unmounts
all file systems and then forcibly reboots (this way all file systems
will be clean but reboot will still be very fast). Finally,
reboot-immediate does not attempt to kill any process or
unmount any file systems. Instead it just hard reboots the machine
without delay. reboot-immediate hence comes closest to a
reboot triggered by a hardware watchdog. All these settings are
documented in systemd.service(5).

Putting this all together we now have pretty flexible options to
watchdog-supervise a specific service and configure automatic restarts
of the service if it hangs, plus take ultimate action if that doesn’t
help.

Here’s an example unit file:

[Unit]
Description=My Little Daemon
Documentation=man:mylittled(8)

[Service]
ExecStart=/usr/bin/mylittled
WatchdogSec=30s
Restart=on-failure
StartLimitInterval=5min
StartLimitBurst=4
StartLimitAction=reboot-force

This service will automatically be restarted if it hasn’t pinged
the system manager for longer than 30s or if it fails otherwise. If it
is restarted this way more often than 4 times in 5min action is taken
and the system quickly rebooted, with all file systems being clean
when it comes up again.

And that’s already all I wanted to tell you about! With hardware
watchdog support right in PID 1, as well as supervisor watchdog
support for individual services we should provide everything you need
for most watchdog usecases. Regardless if you are building an embedded
or mobile applience, or if your are working with high-availability
servers, please give this a try!

(Oh, and if you wonder why in heaven PID 1 needs to deal with
/dev/watchdog, and why this shouldn’t be kept in a separate
daemon, then please read this again and try to understand that this is
all about the supervisor chain we are building here, where the hardware watchdog
supervises systemd, and systemd supervises the individual
services. Also, we believe that a service not responding should be
treated in a similar way as any other service error. Finally, pinging
/dev/watchdog is one of the most trivial operations in the OS
(basically little more than a ioctl() call), to the support for this
is not more than a handful lines of code. Maintaining this externally
with complex IPC between PID 1 (and the daemons) and this watchdog
daemon would be drastically more complex, error-prone and resource
intensive.)

Note that the built-in hardware watchdog support of systemd does
not conflict with other watchdog software by default. systemd does not
make use of /dev/watchdog by default, and you are welcome to
use external watchdog daemons in conjunction with systemd, if this
better suits your needs.

And one last thing: if you wonder whether your hardware has a
watchdog, then the answer is: almost definitely yes — if it is anything more
recent than a few years. If you want to verify this, try the wdctl
tool from recent util-linux, which shows you everything you need to
know about your watchdog hardware.

I’d like to thank the great folks from Pengutronix for contributing
most of the watchdog logic. Thank you!

Footnotes

[1] Though actually most desktops tend to include watchdog
hardware these days too, as this is cheap to build and available in
most modern PC chipsets.

[2] So, here’s a free tip for you if you hack on the core
OS: don’t enable this feature while you hack. Otherwise your system
might suddenly reboot if you are in the middle of tracing through PID
1 with gdb and cause it to be stopped for a moment, so that no
hardware ping can be done…

systemd for Administrators, Part XIV

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/self-documented-boot.html

And
here’s the fourteenth
installment
of

my ongoing series
on
systemd
for
Administrators:

The Self-Explanatory Boot

One complaint we often hear about systemd is
that its boot process was hard to understand, even
incomprehensible. In general I can only disagree with this sentiment, I
even believe in quite the opposite: in comparison to what we had
before — where to even remotely understand what was going on you had
to have a decent comprehension of the programming language that is
Bourne Shell[1] — understanding systemd’s boot process is
substantially easier. However, like in many complaints there is some
truth in this frequently heard discomfort: for a seasoned Unix
administrator there indeed is a bit of learning to do when the switch
to systemd is
made. And as systemd developers it is our duty to make the learning
curve shallow, introduce as few surprises as we can, and provide
good documentation where that is not possible.

systemd always had huge body of documentation as manual
pages
(nearly 100 individual pages now!), in the Wiki and
the various blog stories I posted. However, any amount of
documentation alone is not enough to make software easily
understood. In fact, thick manuals sometimes appear intimidating and
make the reader wonder where to start reading, if all he was
interested in was this one simple concept of the whole system.

Acknowledging all this we have now added a new, neat, little
feature to systemd: the self-explanatory boot process. What do we mean
by that? Simply that each and every single component of our boot comes
with documentation and that this documentation is closely linked to
its component, so that it is easy to find.

More specifically, all units in systemd (which are what
encapsulate the components of the boot) now include references to
their documentation, the documentation of their configuration files
and further applicable manuals. A user who is trying to understand the
purpose of a unit, how it fits into the boot process and how to
configure it can now easily look up this documentation with the
well-known systemctl status command. Here’s an example how
this looks for systemd-logind.service:

$ systemctl status systemd-logind.service
systemd-logind.service - Login Service
	  Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
	  Active: active (running) since Mon, 25 Jun 2012 22:39:24 +0200; 1 day and 18h ago
	    Docs: man:systemd-logind.service(7)
	          man:logind.conf(5)
	          http://www.freedesktop.org/wiki/Software/systemd/multiseat
	Main PID: 562 (systemd-logind)
	  CGroup: name=systemd:/system/systemd-logind.service
		  └ 562 /usr/lib/systemd/systemd-logind

Jun 25 22:39:24 epsilon systemd-logind[562]: Watching system buttons on /dev/input/event2 (Power Button)
Jun 25 22:39:24 epsilon systemd-logind[562]: Watching system buttons on /dev/input/event6 (Video Bus)
Jun 25 22:39:24 epsilon systemd-logind[562]: Watching system buttons on /dev/input/event0 (Lid Switch)
Jun 25 22:39:24 epsilon systemd-logind[562]: Watching system buttons on /dev/input/event1 (Sleep Button)
Jun 25 22:39:24 epsilon systemd-logind[562]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)
Jun 25 22:39:25 epsilon systemd-logind[562]: New session 1 of user gdm.
Jun 25 22:39:25 epsilon systemd-logind[562]: Linked /tmp/.X11-unix/X0 to /run/user/42/X11-display.
Jun 25 22:39:32 epsilon systemd-logind[562]: New session 2 of user lennart.
Jun 25 22:39:32 epsilon systemd-logind[562]: Linked /tmp/.X11-unix/X0 to /run/user/500/X11-display.
Jun 25 22:39:54 epsilon systemd-logind[562]: Removed session 1.

On the first look this output changed very little. If you look
closer however you will find that it now includes one new field:
Docs lists references to the documentation of this
service. In this case there are two man page URIs and one web URL
specified. The man pages describe the purpose and configuration of
this service, the web URL includes an introduction to the basic
concepts of this service.

If the user uses a recent graphical terminal implementation it is
sufficient to click on the URIs shown to get the respective
documentation[2]. With other words: it never has been that
easy to figure out what a specific component of our boot is about:
just use systemctl status to get more information about it
and click on the links shown to find the documentation.

The past days I have written man pages and added these references
for every single unit we ship with systemd. This means, with
systemctl status you now have a very easy way to find out
more about every single service of the core OS.

If you are not using a graphical terminal (where you can just click
on URIs), a man page URI in the middle of the output of systemctl
status
is not the most useful thing to have. To make reading the
referenced man pages easier we have also added a new command:

systemctl help systemd-logind.service

Which will open the listed man pages right-away, without the need
to click anything or copy/paste an URI.

The URIs are in the formats documented by the uri(7)
man page. Units may reference http and https URLs, as well as man and
info pages.

Of course all this doesn’t make everything self-explanatory, simply
because the user still has to find out about systemctl status
(and even systemctl in the first place so that he even knows
what units there are); however with this basic knowledge further
help on specific units is in very easy reach.

We hope that this kind of interlinking of runtime behaviour and the
matching documentation is a big step forward to make our boot easier
to understand.

This functionality is partially already available in Fedora 17, and
will show up in complete form in Fedora 18.

That all said, credit where credit is due: this kind of references
to documentation within the service descriptions is not new, Solaris’
SMF had similar functionality for quite some time. However, we believe
this new systemd feature is certainly a novelty on Linux, and with
systemd we now offer you the best documented and best self-explaining
init system.

Of course, if you are writing unit files for your own packages,
please consider also including references to the documentation of your
services and its configuration. This is really easy to do, just list
the URIs in the new Documentation= field in the
[Unit] section of your unit files. For details see systemd.unit(5). The
more comprehensively we include links to documentation in our OS
services the easier the work of administrators becomes. (To make sure
Fedora makes comprehensive use of this functionality I filed a bug on
FPC
).

Oh, and BTW: if you are looking for a rough overview of systemd’s
boot process here’s
another new man page we recently added
, which includes a pretty
ASCII flow chart of the boot process and the units involved.

Footnotes

[1] Which TBH is a pretty crufty, strange one on top.

[2] Well, a terminal
where this bug is fixed
(used together with a help
browser where this one is fixed
).

The collective thoughts of the interwebz