* Michael Biebl <bi...@debian.org> [2014-05-31 15:09 +0200]: > Am 31.05.2014 14:29, schrieb Elimar Riesebieter: > > severity 739190 grave > > forwarded 739190 pkg-systemd-maintain...@lists.alioth.debian.org > > thanks > > > > > > * Elimar Riesebieter <riese...@lxtec.de> [2014-02-16 17:42 +0100]: > > > >> Package: netenv > >> Version: 0.94.3-30 > >> Severity: normal > >> > >> Don't know how to debug? > >> "systemctl netenv start" doesn't start the dialog. > >> > >> Running netenv by sysvinit everthing seems to be ok. > > Under systemd all services run in a defined context. > This also means you can't prompt for input by reading from the console. > > # X-Interactive: true > > as used by the netenv sysv init script does not work by design. See [1]:
[...] ACK. My intention ist to configure my laptops to choose either: - connect to a nis network - connect to a a nisless network This I manged flawlessly via netenv. As nis ist started before any networkmanger like wicd or nm, there is no way to slowdown nis to wait until network is avail. A non providing nisserver caused by no network slows down a machine useless at all. > [1] http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities/ Elimar -- Obviously the human brain works like a computer. Since there are no stupid computers humans can't be stupid. There are just a few running with Windows or even CE ;-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
