Anatoly Oreshkin <[EMAIL PROTECTED]> writes:
> afs_syscall(0x1c, 0xa, 0x5029a, 0, 0xbfffc430) = -1 ENOSYS (Function not
> implemented)
> ...
>
> It looks like that afsd forks necessary demons rx listener,
> rx callback listener, rxevent daemon. But these demons exit abnormaly.
>
> What may be the reason ? Any hints ?
That's your hint... The afsd process can't call afs_syscall because
it's returning ENOSYS. This implies the afs_syscall did not get
properly installed into the kernel.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-devel
