Re: how to assert user input to fifo to then read from it

[Dennis Williamson]

On Thu, Aug 25, 2022, 7:31 AM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com>
wrote:

>
>
> On Thu, Aug 25, 2022, 14:14 Dennis Williamson <dennistwilliamson@gmail.com>
> wrote:
>
>>
>>
>> On Thu, Aug 25, 2022 at 4:39 AM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com>
>> wrote:
>>
>>> im doing some apt update cmds script
>>> in there i realized i need detached input for , when as dedicated auto
>>> updater used , a question appears , to answer this
>>> ( seeing by log then reacting to via printf to fifo , and checking then
>>> log
>>> further )
>>>
>>> the script yet is attached
>>> the in question is line 20 , it does exec <"$fi"
>>> .. and my question is what previously to exec to put scripts stdin ( may
>>> not be tty .. ? ) into that fifo , then that the exec < that_fifo
>>>
>>> understood halfways ?
>>>
>>> // greets , alex xmb
>>>
>>
>> Chances are you need to select the correct options for your apt commands
>> rather than trying to inject input.
>>
>> Look up how to use DEBIAN_FRONTEND=noninteractive and Dpkg::Options and
>> seek further help in a Debian or apt forum.
>>
>
> hi .. :)
> about this , im pretty sure : i set noninteractive and priority none or
> low whatever the lowest was , and tho i modded a conf file manually , and
> then somewhen the autoupdater wasnt well cause it asked about such a fatal
> as replace conf , and no user input was , <&- at most , if even
> ..so i need my 'keep input open' solution i ask for , me thinks
>
> best greets :))
>
> --
>> Visit serverfault.com to get your system administration questions
>> answered.
>>
>
There are Dpkg::Options that deal with replacing or keeping the config.

>