App installieren
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Anmerkung: This feature may not be available in some browsers.
Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
New server status page
- Ersteller Sir Ulli
- Erstellt am
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
ganz interessant
Glossary
Programs
* Data-driven web pages: Public web pages that require database access to be generated. Pages like the forums, or ones that contain statistics or client version information, etc. are occasionally turned off (by hand) when the database is down.
* Scheduler: Determines what work is going to be sent to/received from requesting clients. If this is off, you cannot send any results or receive any workunits.
* Feeder: Fills up the scheduler work queue with workunits ready to be sent. The scheduler is too busy handling transaction with clients so the feeder does this job.
* File_deleter: Deletes input/output files when no longer needed. This program keeps our upload/download disks as clean as possible.
* Transitioner: Handles state transitions of workunits and results. Basically, the transitioners keep track of the many, many results in progress and makes sure they properly move down the pipeline. It is always asking the questions: Is this workunit ready to send out? Has this result been received yet? Is this a valid result? Can we delete it now? Since there are always a large set of results in progress, we need to run several transitioners in tandem to keep up with the workunit/result flow. The Transitioner queue tell you how many workunits/results are waiting to move down the pipeline. A large number means there is a problem somewhere in our backend server system.
* Sah_validate: Validates SETI@home results by comparing them with similar results returned by other users. If enough results for the same workunit have been returned, the validator compares the data and issues credit to all responsible users accordingly. The Validator queue tells you how many results are currently awaiting validation/credit.
* Sah_assimilator: Takes scientific data from validated results and puts them in the SETI@home master database for later analysis.
* Sah_splitter: Reads tapes (or tape images on disk) containing raw telescope data and creates workunits for the BOINC/SETI@home clients.
Hosts
* klaatu: Sun D220R (2 x 440MHz Sparc, 2 GB RAM)
* koloth: Sun D220R (2 x 440MHz Sparc, 1 GB RAM)
* kryten: Sun D220R (2 x 440MHz Sparc, 2 GB RAM)
* galileo: Sun E3500 (6 x 400MHz Sparc, 6 GB RAM)
* milkyway: Sun U60 (2 x 400MHz Sparc, 1 GB RAM)
* philmor: Sun U10 (1 x 350MHz Sparc, 1 GB RAM)
so weiss man hoffentlich immer woran es liegt
http://setiweb.ssl.berkeley.edu/sah_status.html
mfg
Sir Ulli
Glossary
Programs
* Data-driven web pages: Public web pages that require database access to be generated. Pages like the forums, or ones that contain statistics or client version information, etc. are occasionally turned off (by hand) when the database is down.
* Scheduler: Determines what work is going to be sent to/received from requesting clients. If this is off, you cannot send any results or receive any workunits.
* Feeder: Fills up the scheduler work queue with workunits ready to be sent. The scheduler is too busy handling transaction with clients so the feeder does this job.
* File_deleter: Deletes input/output files when no longer needed. This program keeps our upload/download disks as clean as possible.
* Transitioner: Handles state transitions of workunits and results. Basically, the transitioners keep track of the many, many results in progress and makes sure they properly move down the pipeline. It is always asking the questions: Is this workunit ready to send out? Has this result been received yet? Is this a valid result? Can we delete it now? Since there are always a large set of results in progress, we need to run several transitioners in tandem to keep up with the workunit/result flow. The Transitioner queue tell you how many workunits/results are waiting to move down the pipeline. A large number means there is a problem somewhere in our backend server system.
* Sah_validate: Validates SETI@home results by comparing them with similar results returned by other users. If enough results for the same workunit have been returned, the validator compares the data and issues credit to all responsible users accordingly. The Validator queue tells you how many results are currently awaiting validation/credit.
* Sah_assimilator: Takes scientific data from validated results and puts them in the SETI@home master database for later analysis.
* Sah_splitter: Reads tapes (or tape images on disk) containing raw telescope data and creates workunits for the BOINC/SETI@home clients.
Hosts
* klaatu: Sun D220R (2 x 440MHz Sparc, 2 GB RAM)
* koloth: Sun D220R (2 x 440MHz Sparc, 1 GB RAM)
* kryten: Sun D220R (2 x 440MHz Sparc, 2 GB RAM)
* galileo: Sun E3500 (6 x 400MHz Sparc, 6 GB RAM)
* milkyway: Sun U60 (2 x 400MHz Sparc, 1 GB RAM)
* philmor: Sun U10 (1 x 350MHz Sparc, 1 GB RAM)
so weiss man hoffentlich immer woran es liegt
http://setiweb.ssl.berkeley.edu/sah_status.html
mfg
Sir Ulli
Ähnliche Themen
- Antworten
- 0
- Aufrufe
- 434
- Antworten
- 0
- Aufrufe
- 354
- Antworten
- 0
- Aufrufe
- 318