I will have a look at #811823 later on, but for a start:
We have /var mounted as a separate partition on all installations
on which we see the idmapd start-up problems. The same goes for
/usr and /tmp.
Cheers,
Alex
On 19/07/11 18:59, Steve Langasek wrote:
> iFred,
>
> I could not reproduce this problem even before I made that change to
> /etc/init{idmapd,gssd}.conf in oneiric.
>
> Something has just occurred to me, however, Could it be that the users
> seeing this bug all had /var as a separate partition? In thas case, the
> rpc_pipefs job would fail if /var isn't yet mounted, causing the idmapd
> job to *continue* in spite of the failure, and resulting in this error.
>
> In that case, it seems that my recently proposed SRU to drop the
> rpc_pipefs job may have precisely the right effect, if entirely by
> accident.
>
Hi Steve,
I will have a look at #811823 later on, but for a start:
We have /var mounted as a separate partition on all installations
on which we see the idmapd start-up problems. The same goes for
/usr and /tmp.
Cheers,
Alex
On 19/07/11 18:59, Steve Langasek wrote: idmapd, gssd}.conf in oneiric.
> iFred,
>
> I could not reproduce this problem even before I made that change to
> /etc/init{
>
> Something has just occurred to me, however, Could it be that the users
> seeing this bug all had /var as a separate partition? In thas case, the
> rpc_pipefs job would fail if /var isn't yet mounted, causing the idmapd
> job to *continue* in spite of the failure, and resulting in this error.
>
> In that case, it seems that my recently proposed SRU to drop the
> rpc_pipefs job may have precisely the right effect, if entirely by
> accident.
>