1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

how to identify when boot occurs

Discussion in 'Legacy Windows' started by tiwang, 2005/03/30.

Thread Status:
Not open for further replies.
  1. 2005/03/30
    tiwang

    tiwang Inactive Thread Starter

    Joined:
    2005/01/14
    Messages:
    53
    Likes Received:
    0
    Hi out there

    I need to find a way to identify - from a service - if there server just is starting up or if it has been running and my service is being restarted - and some might ask why this is important - this is caused by some problems when handling tapes - we have a service which backups the transaction log on tape from a sybase database in MTF. But - we have a minor problem - when the server starts in the intial boot and the services are started in a more or less parallel order we get a conflict between RSM and our services when accessing the tape device. So therefore I need to find a way to identify if I am in a normal boot sequence when the service is starting or if it has been running and my service just has been restarted because of tape maintaince etc. Of course I could just take a look at "uptime" and wait five minutes or so - but isn't there a way to tell if we still are in the boot phase ?

    regards /thomas iwang
     
  2. 2005/03/30
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    why dont you just make your service dependant on RSM?
     

  3. to hide this advert.

  4. 2005/03/30
    tiwang

    tiwang Inactive Thread Starter

    Joined:
    2005/01/14
    Messages:
    53
    Likes Received:
    0
    hi joe
    thanks - the idea is ok - but - because the handling of tapes are very "time consuming" we risk to get the same contention problem when the tape is in the phase of rewinding. RSM returns a running before all devices are fully initialised - hereby will the start-up of services continue because it has acknowledged running and we will then get a contention problem when "our" service try to open the tape device also. So the easiest workaround was f.ex. to take boot time + 5 minutes or wait for RSM to be running + 5 minutes - but - cannot be that it is that hard to figure out where in the boot phase we are - when I look at unix where we have a simple - and quite elegant - concept of run-levels and rc-scripts which either are executed sequentielle or in parallel - and here I cannot even figure out if I am in a boot phase or running several hours....
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.