I want to use fedora on a userless Windows Server 2003 machine. Until now I
must login as administrator and start fedora with the start script
"fedora-start mckoi". After each manual stop with the stop script
"fedora-stop" and a new manual start, I got:
"WARN 27:51 AbstractBlockFile> File size was not a multiple of blocksize:
"WARN 27:54 XANodePoolImpl> Node pool metaroot file for triple store
"C:\fedora2_0_resourceIndex\nodePool" has invalid number of blocks: 21845"
"WARN 27:54 ManagedBlockFile> NOTE: Correcting size of file:
An administrator shutdown/reboot does the same thing and corrupts my fedora
repository. Our admin is not instructed in the use of fedora and he has no
time for managing each software module on each machine, so the termination
of fedora is not under my control and I need a stable way running fedora.
To correct the resource index corruption, I have added the patch for
restoring the resource index, but this tool requires also interaction from
an admin / user.
So my questions to the fedora team and the fedora users:
- How can I manage a fedora server installation without user interaction ?
- How can I install fedora as a service on Windows Server 2003, so fedora
starts when the machine boots up and terminates correctly !!! (without
corrupting the resource index !!!) when the machine is turned off.
- What are the steps to get fedora running stable on a userless server in a
far away server room ?
I hope someone could give me some hints.