On Thu, 11.11.10 11:01, Kay Sievers ([email protected]) wrote:
> > What's wrong?
>
> It's a bug in the systemd filter list. systemd has a list of stuff to
> ignore, along with the API filesystems it uses itself. The
> remount-api-vfs tool uses the entire list, so this goes wrong with
> /proc/b
On Thursday 11 November 2010 11:01:21 Kay Sievers wrote:
> On Thu, Nov 11, 2010 at 10:34, Andreas Jaeger wrote:
> > I noticed for some time that systemd-remount-api-vfs is in the failed
> > state and found now the following in the log files
> >
> > <4>[3.063357] systemd[1]: systemd 11 running
On Thu, Nov 11, 2010 at 10:34, Andreas Jaeger wrote:
>
> I noticed for some time that systemd-remount-api-vfs is in the failed state
> and found now the following in the log files
>
> <4>[ 3.063357] systemd[1]: systemd 11 running in system mode. (+PAM
> +LIBWRAP +AUDIT +SELINUX +SYSVINIT; sus
I noticed for some time that systemd-remount-api-vfs is in the failed state and
found now the following in the log files
<4>[3.063357] systemd[1]: systemd 11 running in system mode. (+PAM +LIBWRAP
+AUDIT +SELINUX +SYSVINIT; suse)
<4>[3.142518] systemd[1]: Set hostname to .
<4>[4.598
