10.12.2018 23:26, Boyce, Kevin P [US] (AS) пишет:
> I seem to be struggling with what should be a very basic operation. I've
> seen similar questions posted to the list here and none of them are really
> adequate.
>
> I'm trying to prompt the user to ask a question as the system is coming up
>
Am 10.12.18 um 22:06 schrieb Boyce, Kevin P [US] (AS):
> I'm sure Redhat has implemented some services of type Simple.
>
> However, my service is oneshot, and what you're saying is there's no way for
> me to force any other service to wait until my service exits before bootup
> continues?
Typ
I'm sure Redhat has implemented some services of type Simple.
However, my service is oneshot, and what you're saying is there's no way for me
to force any other service to wait until my service exits before bootup
continues?
This doesn't seem right given that systemd can wait for a password to
Am 10.12.18 um 21:26 schrieb Boyce, Kevin P [US] (AS):
> I seem to be struggling with what should be a very basic operation.
> I’ve seen similar questions posted to the list here and none of them are
> really adequate.
>
> I’m trying to prompt the user to ask a question as the system is coming
I seem to be struggling with what should be a very basic operation. I've seen
similar questions posted to the list here and none of them are really adequate.
I'm trying to prompt the user to ask a question as the system is coming up (so
the system can configure it's network and other things bas
On Mon, Dec 10, 2018 at 2:12PM Lennart Poettering wrote:
> Or this is about enable/disabling rfkill at subsequent boot, using
> "systemctl enable rfkill-block@xyz.service"? This kinda conflicts with
> the save/restore logic systemd-rfkill@.service
Thanks for explanation, I will drop rfkill-block@.
Right when I feel I started to better understand Possession and Keyrings, I
had this:
> keyctl describe 14242397
14242397: alsw-v-- 1002 100 user: keyInUsr
> keyctl print 14242397
mySecret-1
How can I read a key when no one has read rights? Is there some caching
going on? Some
On Mo, 10.12.18 14:29, Michael Biebl (mbi...@gmail.com) wrote:
> > > but these parameter cannot modify the behaviour.
> > > Is there some way to do it ?
> >
> > No there is not. This is compiled in and global. You can turn off all
> > status output though…
>
> It's hard-coded in
> https://github.c
Am Mo., 10. Dez. 2018 um 14:26 Uhr schrieb Lennart Poettering
:
>
> On Mo, 10.12.18 13:47, Paolo Minazzi (paolo.mina...@mitrol.it) wrote:
>
> > but these parameter cannot modify the behaviour.
> > Is there some way to do it ?
>
> No there is not. This is compiled in and global. You can turn off all
On Mo, 10.12.18 13:47, Paolo Minazzi (paolo.mina...@mitrol.it) wrote:
> but these parameter cannot modify the behaviour.
> Is there some way to do it ?
No there is not. This is compiled in and global. You can turn off all
status output though…
Lennart
--
Lennart Poettering, Red Hat
On Mo, 10.12.18 13:53, Karel Zak (k...@redhat.com) wrote:
65;5402;1c
> On Tue, Nov 27, 2018 at 07:16:04PM +0100, Stanislav Brabec wrote:
> > Sami Kerola wrote:
> > That said,
> > > getting a clarification from Jochen would nice because otherwise we are
> > > simply guessing.
> >
> > Jochen Keil alr
Am 10.12.18 um 14:09 schrieb Paolo Minazzi:
> Il 10/12/2018 14:00, Reindl Harald ha scritto:
>> no and this all sounds like seeking a solution for a non existing
>> problem! what in the world do you achieve whne your system hangs around
>> at boot and don't tell you any reason?
>>
>> "TimeoutStar
Il 10/12/2018 14:00, Reindl Harald ha scritto:
no and this all sounds like seeking a solution for a non existing
problem! what in the world do you achieve whne your system hangs around
at boot and don't tell you any reason?
"TimeoutStartSec=" controls the limit so that it won't get killed
premat
Am 10.12.18 um 13:47 schrieb Paolo Minazzi:
> Dear all,
> I'm studying systemd to write a service that start and is executed
> before a local-fs.target.
> To do my test, I have written a simple service.
>
>
> [Unit]
> Description=myservice
> DefaultDepende
Dear all,
I'm studying systemd to write a service that start and is executed
before a local-fs.target.
To do my test, I have written a simple service.
[Unit]
Description=myservice
DefaultDependencies=no
[Service]
Type=oneshot
ExecStart=/bin/bash -c "ech
On Tue, Nov 27, 2018 at 07:16:04PM +0100, Stanislav Brabec wrote:
> Sami Kerola wrote:
> That said,
> > getting a clarification from Jochen would nice because otherwise we are
> > simply guessing.
>
> Jochen Keil already left SUSE and I have no contact e-mail to him.
>
> But I got complain that i
On Fri, Dec 7, 2018 at 9:47 PM Dinesh Prasanth Moluguwan Krishnamoorthy <
dmolu...@redhat.com> wrote:
> Oh damn! Yes. It worked!
>
> So, my next question would be "how to avoid it?"
>
> To expand a bit more:
>
> I want to make these passwords inaccessible outside the systemd service
> even by that
I want to make these passwords inaccessible outside the systemd service
even by that USER. (or does it sound something contradictory?)
In that case you cannot use the user keyring, as any key there will always be
available to the user. You will either need to use the process keyring, or the
sess
18 matches
Mail list logo
