| |||||||||||||
|
| |||||||||||||
Systemd and Fedora 14Systemd and Fedora 14Posted Aug 26, 2010 14:23 UTC (Thu) by rahulsundaram (subscriber, #21946)In reply to: Systemd and Fedora 14 by etienne Parent article: Systemd and Fedora 14
the service file associated can instruct systemd to start it by default or on socket activation. Either is possible.
(Log in to post comments)
Systemd and Fedora 14 Posted Aug 26, 2010 15:11 UTC (Thu) by etienne (subscriber, #25256) [Link]
So the distribution default will be to start sound on socket activation, that is the normal setup.
Now, the computer has booted - how to hide that socket for the next 10 minutes, I know that beep() will be called by the next command - and I want beep() to fail? Or, I am in a plane, I want the network OFF so that all applications will start in their "off-line" mode.
Systemd and Fedora 14 Posted Aug 26, 2010 15:16 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link]
You disable the particular services. Have you tried systemd at all? I am not sure where the confusion is coming from.
Systemd and Fedora 14 Posted Aug 27, 2010 9:23 UTC (Fri) by Kamilion (guest, #42576) [Link]
> Or, I am in a plane, I want the network OFF so that all applications will start in their "off-line" mode.
Um... Flick your hardware RF kill switch to 'wireless off'?
But your implied 'network OFF' is a relatively heavy sledgehammer if you're nitpicking socket activation; what about lo or vbox/vmware networks?
In closing, a nitpick of my own: You insane people using the PC speaker beep in init should be SHOT with a SONIC CANNON. ;)
|
|
||||||||||||