Re: Manual step in upgrade process for a FSWC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, Aug 30, 2023 at 8:46 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
On Wed, Aug 30, 2023 at 11:59:18AM +0200, Iker Pedrosa wrote:
> Hi,
>
> I intend to switch pam_userdb's database provider from BerkeleyDB to GDBM
> and I'm writing a Fedora System-Wide Change
> <https://fedoraproject.org/wiki/Changes/PamBerkeleyDBtoGdbm> for Fedora 40.
> The upgrade process would involve a manual procedure where the user needs
> to run a conversion tool for the database. Is this acceptable?
>
> An automation process could be created, but the location of the database is
> configurable, which increases its complexity and effort. Especially for a
> PAM module that is not widely used. Another option I can think of is to
> automate the conversion process for the default location, and leave the
> manual conversion for those using a tuned location. Would that be
> acceptable?

Will the new version emit some kind of error telling users what needs to
happen?

It'll log an error but it will be generic, like "user_lookup: could not open database `PATH': %m"
 

Will that 'fail closed'? ie, no access granted until the db is
converted?

I don't understand this question.
 

I don't suppose it would be possible to just run the convert at runtime?
ie, if old db is found at the configured location convert it to the new
version?

There are several packages relying in BerkeleyDB and the database team is working in a tool to convert them. So I'd like to avoid replicating the code for each and every package, and instead rely on their tool.
 

kevin
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--

Iker Pedrosa

Senior Software Engineer, Identity Management team

Red Hat

Txapela (gorria) buruan eta ibili munduan

(Red) hat on his head and walk the world

Basque proverb   

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux