>
> >
> > Antony Suter wrote:
> > >=20
> > > Guillaume Rousse wrote:
> > > >
> > > > Bryan Paxton a =E9crit :
> > > > >
> > > > > When you try to start xfs and it just says passed ?
> > > > > The lock file gets created and yada yada, but the server doesn't star=
> > t up, it
> > > > > simply says passed
> > > > >
> > > > > What does this mean ?
> > > > It means failure :-)
> > > > Quick fix : change your /etc/init.d/xfs script by commenting actual
> > > > launch command, and launch xfs directly:
> > > > su xfs -c "xfs -port -1 -daemon" -s /bin/sh
> > > > instead of
> > > > daemon --check xfs su xfs -c \"xfs -port -1 -daemon\" -s /bin/sh
> > > >
> > > > Seems there have been some change in xfs configuration recently, that
> > > > affect some users (already two thread on this topic) onyl. Maybe
> > > > something linked to incremental or direct XFree86 upgrade N
> > >=20
> > > I want to point out to the Mandrake team that I also have this problem.
> > > I need to remove the words "daemon --check" from /etc/rc.d/init.d/xfs so
> > > that my xfs server will start as normal.
> >
> > This problem has now been truely fixed for me.
> >
> > Somehow I did not have the latest pam.rpm on my system.
> >
> > The recent upgrades to sh-utils and pam have fixed it for me.
> >
> > --
> > - Antony Suter ([EMAIL PROTECTED]) "Examiner" openpgp:71ADFC87
> > - "And how do you store the nuclear equivalent of the universal solvent?"
> >
> >
> I have the same problem. The xfs-server just doesn't get to work. I tryed the above
>but it doesn't help.
>
>
Seems that my mirror was a bit slow. Upgraded pam + sh_utils and it works again
