From: robin_listas@es.invalid   
      
   On 20/03/2021 15.58, Malcolm wrote:   
   > On Sat, 20 Mar 2021 13:31:38 +0100 "Carlos E.R."    
   wrote:   
   >> On 19/03/2021 23.37, Malcolm wrote:   
   >>> On Fri, 19 Mar 2021 22:13:49 -0000 (UTC) William Unruh    
   wrote:   
   >>>> On 2021-03-19, Malcolm  wrote:   
   >>>>> On Thu, 18 Mar 2021 12:05:25 +0100 "Carlos E.R."  wrote:   
   >>>>>   
   >>>>>> Cron (or timer) is worse: no terminal assigned, so echoing the   
   >>>>>> bell character will not sound.   
   >>>>> Hi   
   >>>>> The assign one in the service....?   
   >>>>> Environment=TERM=linux   
   >>>>   
   >>>> No. That just tells the system what type of terminal emulator to   
   >>>> use. It does not assign a tty to the service. Ie, when cron   
   >>>> starts, where is it supposed to send the output and where get its   
   >>>> input from. It assumes that there is nowhere to send the output to   
   >>>> ( except perhaps to mail) and nowhere to get input from.   
   >>>>>   
   >>> Hi   
   >>> Sure, that's just a snippet for assigning a terminal in a service.   
   >>> As per my earlier posts shows a full systemd service on how I do it   
   >>> with with the likes of htop running on tty12....  Have lots of   
   >>> things running on tty's as have no need to log in, just switch...   
   >>   
   >>   
   >> Wait, you are saying that the line:   
   >>   
   >>   
   >> Environment=TERM=linux   
   >>   
   >>   
   >> is a specific systemd concoction that actually assigns some type of   
   >> virtual terminal to the timer job?   
   >>   
   >> Well, this is news to me. It was not clear in your post, either.   
   >>   
   >> That would solve the issue of doing a beep (which I can send to   
   >> /dev/console instead), but does not solve the issue of having proper   
   >> sound from a cron job (as the OP requested), or even a service (I   
   >> want to play sound from services and it doesn't work - the samples I   
   >> posted belong to systemd services I have).   
   >>   
   >> The solution would be running pulse as a global daemon so that users   
   >> can access it before the desktop is running, or besides it.   
   >>   
   > Hi   
   > It's a real terminal on the selected tty, so not sure console would   
   > work....   
      
   Ah, a terminal has to be selected first. Then the situation is the same   
   as with cron.   
      
      
   > Maybe this would help: https://bbs.archlinux.org/viewtopic.php?id=213751   
      
   That's about using sound during boot. It will give me ideas, thankyou.   
      
   I want sound just after boot, and much later (like a clock that speaks   
   the time, for instance; I had that and it broke with 15.2). The first   
   step will be running pulse as an independent daemon, started before the   
   desktop, so that any user can access it.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)