Merci Pierre et Flup,
mais après 2 heures de surf sur les differents sites OS X, j'ai enfin trouver la solution à mon problème, et qui je crois va intéresser d'autres personnes.
La chose que j'ai fait et qu'il ne faut surtout pas faire c'est de mettre l'autorisation "tout utlisateurs"du disk principal sur "aucune (none)" au lieu de la laisser sur "lecture seule".
Après mettre connecté depuis un autre mac sous OS X avec "Admin Server" pour remettre l'autorisation sur "lecture seule", tout mes problèmes on disparus (fenêtre de login et temps de connexion).
Ci-dessous le post original copier sur le site de MacOSXhints (avant d'essayer la solution ci-dessous, essayez la mienne, qui est plus simple et pas dangereuse) :
"
OS X Server Blue Screen of Death problem
Thu, Jul 19 '01 at 03:56PM from: scottboms
It seems that OS X Server 10.0x users may find themselves in Windows land with a blue screen of death and virtually no way back without having to resort to reloading the OS. I'm not sure if this is specifically related to the MP G4's (I'm using a dual 533MHz G4 with 640MB of RAM and 2 internal 40GB ATA drives),but I think it's worth noting anyway.
In searching through Apple's Discussion boards I came across a couple of posts with solutions and thought it would be useful to post that info here as well.
Regards,
Scott
[Editor's note: If you have Mac OS X Server and are experiencing the blue screen, read the rest of this article for a couple of proposed solutions.]
WHAT NOT TO DO:
When modifying the Apple File Sharing access for however many drives are in your server, DO NOT set the sharing access for Everyone to 'None'. You may be fine for a while, but eventually you will get a blue screen and nothing else. Rebooting will not help.
HOW TO FIX IT:
You can fix this by booting into Single User mode (Cmd-S) and typing the commands below, but I do not recommend this as it opens up every file to all users! Obviously this is a security problem.
/bin/fsck -y; /bin/mount -vw /; chmod a+rwx /;
The better solution is to avoid the problem in the first place by not changing those settings. Hopefully Apple will fix this issue in the 10.1 update whenever it is released in September. So far I think the server is great, but this has really ticked me off and caused a lot of wasted time. Good luck to anyone else out there using the Server version of OS X.
<BLOCKQUOTE><font size="1" face="Verdana, Geneva">quote:</font><HR>Le savoir ne vaut que si il est partagé
<HR></BLOCKQUOTE>