OK, that seems reasonable, I'll look forward to the patch.
On Wed, Apr 17, 2019 at 12:35:48AM +0200, Jaime Caamaño Ruiz wrote: > > On any given system, I would expect ovsdb-server to run as the same > > user > > every time. Is there a reason to sometimes use a different user? > > Well, changing from root which was the only supported option in the > past and current default to a different user (like the suggested > openvswitch), this one time, might be somewhat common. And the scenario > that I am looking at is suporting a pianless upgrade through it. > > So if that makes sense to you, I will go ahead with the patch. > > BR > Jaime. > > -----Original Message----- > From: Ben Pfaff <[email protected]> > To: [email protected] > Cc: [email protected] > Subject: Re: [ovs-discuss] Handling conf.db ownership on OVS_USER_ID > changes > Date: Tue, 16 Apr 2019 15:25:24 -0700 > > On Tue, Apr 16, 2019 at 11:32:21PM +0200, Jaime Caamaño Ruiz wrote: > > When sysconfig OVS_USER_ID is changed to a different user, it > > requires > > a manual ownership change of the OVS conf.db database if existing or > > otherwise ovsdb-server will fail to (re)start. I was wondering if I > > am > > missing any particular reason why this is change of ownership is not > > automatically being handled through the service unit file as it is > > being done with other items. > > On any given system, I would expect ovsdb-server to run as the same > user > every time. Is there a reason to sometimes use a different user? > > Or, perhaps you are saying that, just before invoking ovsdb-server, the > service unit should chown (or whatever) the database file to the user > that it is going to use to invoke ovsdb-server. That might be > reasonable, but no one has thought to do it yet. Do you want to submit > a patch? > > Thanks, > > Ben. > _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
