activation timeout and slow systems

[Colin Walters]

I know this has been discussed before but I haven't found a good search query for it.

This bug was reported recently: https://bugzilla.redhat.com/show_bug.cgi?id=1888565

Which is basically the 25s activation timeout.  As I noted in the bug I suspect the reporter has a slow system.  On one hand of course if we can't start rpm-ostreed in 25s the user is probably going to have a bad time with the OS in general; that said I think there may partially be rpm-ostree specific problems here in that we're doing too much before we grab the bus name.

I think this type of issue can be exacerbated by systemd's default parallelization - systemd (AFAIK) is unaware of IO limitations and piling on various bus-activated services on slow systems is going to make it much more likely we hit this timeout.

My recollection is that at some point there was an effort to bump this...but it may not have happened?