cached update flaws...

[Rong-en Fan]

On 7/9/07, Alexander Leidinger <Alexander at leidinger.net> wrote:
> Hi,
>
> somehow cached doesn't work as I think it should work. I have a jail
> in which I use cached. There I wanted to install doxygen. As part of
> this cups (dependency from qt) is build. The cups port adds a cups
> user and group. After adding the group/user the configure script
> checks for the user. This fails as cached doesn't know about the added
> user. I have to restart cached to see the user/group (tested with "pw
> groupshow cups").
>
> Are my expectations about cached wrong, or is it misbehaving?

I encountered the same problem few days ago. But I forget
which port I was installing.

> And while we are at it, is there really a need to print the cached
> version number and the fact that it was developed during GSoC 2005 at
> each start? It clutters the visual appearance at boot time.

I feel the same.

BTW, is there any plan to enable cached by default in 7.0?

Regards,
Rong-En Fan
>
> Bye,
> Alexander.
>
> --
> Lord, defend me from my friends; I can account for my enemies.
>                 -- Charles D'Hericault
>
> http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID = B0063FE7
> http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID = 72077137
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>