Re: why EsounD does not start with /etc/init.d/esound start ?

From: Patrick Ouellette (frizzgrig_at_netscape.net)
Date: 07/30/04

  • Next message: Griffin Palmer: "Re: What's blocking Port 25?"
    Date: Fri, 30 Jul 2004 08:08:58 -0400
    To: Miernik <miernik@ctnet.pl>
    
    

    miernik@ctnet.pl wrote:
    > Why EsounD is not started with something like /etc/init.d/esound start
    > like all other daemons, only it is started as a user logs in, well, in
    > fact I don't know very well what starts EsounD, but I have big
    > problems with it, it's a mess-up.

    I is not a "mess-up". If you are using EsounD in a multiple machine,
    multiple user environment (say a University computing lab), the last
    thing you want is to have someone send sounds to all the machines (or
    one machine).

    >
    > First of all, I have a machine on which I want to run EsounD, but I do
    > not run any Gnome or KDE on it, I don't even have a monitor or
    > keyboard connected to that machine. I only log in with ssh, and even
    > that I do rarely.
    >
    > This machine has connected speakers, and what I want to do is to play
    > sound over the network from an app running on a different machine on
    > that machine. Otherwise I would not want a sound daemon at all.

    You can set up your own /etc/init.d/esound script to start it on your
    system. Use the skeleton script in /etc/init.d and then use the update
    script to place the links to it for the run levels you want to start or
    stop the daemon in.

    >
    > Why don't package EsounD like all other daemons, so that when I do
    > aptitude install esound
    > everything gets set-up properly and running automagically at each
    > bootup from /etc/init.d/esound and that all users can play sound
    > through the daemon. I find it really strange that EsounD is run as one
    > user, becasue all other users cannot play sound through it then.

    If Esound were run as a user (say user esd) that introduces one more
    potential security hole, and one more system user to deal with for no
    real benefit.

    Pat

    pouelle@debian.org
    frizzgrig@netscape.net

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Griffin Palmer: "Re: What's blocking Port 25?"

    Relevant Pages

    • Re: Confused about init scripts expectations
      ... I am developing a daemon application to handle datalogger ... I have developed the init script that is ... I attempt to start the daemon using the services configuration GUI ... figure is that the EOF signal is not being received by the program. ...
      (Fedora)
    • Debian PHP jabber client deamon
      ... to prevent PHP stopping the script. ... // disconnect from the Jabber server ... Here's the daemon script for running it in Debian. ... # Gracefully exit if the package has been removed. ...
      (comp.lang.php)
    • Re: Confused about init scripts expectations
      ... I am developing a daemon application to handle datalogger ... I have developed the init script that is ... on the command line to start and stop the daemon process. ... I attempt to start the daemon using the services configuration GUI ...
      (Fedora)
    • Re: rc scripts
      ... startup script so that it parses rc.conf for variables. ... load_rc_config openntpd ... resort to running 'ntpd -gq' at system startup, ... ntpd daemon after the fact. ...
      (freebsd-questions)
    • [HPADM] Re: Startup Script Question
      ... Subject: Startup Script Question ... I have the following line for the start option to launch ... > boot, the startup script launches the daemon, but then the ...
      (HP-UX-Admin)