Boston Linux & UNIX was originally founded in 1994 as part of The Boston Computer Society. We meet on the third Wednesday of each month at the Massachusetts Institute of Technology, in Building E51.

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] SysVinit vs. systemd

On Mon, Sep 15, 2014 at 1:26 PM, Richard Pieri <richard.pieri at> wrote:
> Any
> random console tool /can't/ act the same as a daemon and as a console
> tool. UNIX and Linux don't work that way.

Yes, making legacy programs work in modern lights-out headless
virtualization farms is hard.

Having built wrapper scripts to make a server program
self-resurrecting (not using an OS off-the-shelf tool as we had a
bespoke recovery framework that worked across Solaris, AIX, RedHat), i
concur that programs that don't intend to play nice with
stop/start/restart frameworks are a pain to package, sometimes hard,
sometimes impossible.  If you redirect all 3 standard STDIO handles as
you should in a wrapper, it can't wait for STDIN, but it may still try
to prompt Console or pop up a X dialog in some rare branch of code.

I've also had a Windows C++/MFC server program put the
dump-or-terminate dialog up on the server's console, defeating
auto-restart. (So we had to change the default DrWatson setting, which
was same on server as on workstations, so wrong.)

Bill Ricker
bill.n1vux at

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /