[BUG in 6.0.0-6.0.2] Config>Availability

Viewing 5 posts - 1 through 5 (of 5 total)
  • Back to forum
    Posted in: Muster usage
  • mdsTutor
    29th January 2010 at 12:38 am #14365

    Hi Leonardo,

    “Logon check>Make client unavailable on user logging” and “Unavailable” Time rules seem to have no effect.

    Instances that should be made unavailable (due to users logged in or time rule) still show the green icon and still pick up jobs.

    After changing the config, I have done Soft Restart on the affected instances.

    The time rules I set are
    1)Monday-Thurday 0700-2059 Unavailble
    2)Friday-Friday 0700-1705 Unavailable

    Here is the Behaviour block of rc.conf from one of the affected instances.

    default_process_priority = 1
    drive_mapping =
    enable_nt_automapping = 1
    jobs_start_timeout = 60
    kill_on_lost_connection = 1
    start_paused = 0
    suppress_error_check = 0
    time_rules = 0#0# 1/ 1/2010/ 7/ 0# 4/ 1/2010/20/59?0#0# 5/ 1/2010/ 7/ 0# 5/ 1/2010/17/ 5?
    time_rules_default = 1
    time_rules_waitproc = 0
    process_username =
    process_user_pwd =
    logon_check = 1
    logon_checkremote = 0
    logon_waitpacket = 1
    rules_makecontrollable = 1
    substitution_paths =

    Thanks
    Link

    mdsTutor
    29th January 2010 at 12:44 am #15045

    On instances where “Make client unavailable on user logging” is ignored, the user is logged on locally.

    Leonardo Bernardini
    2nd February 2010 at 10:09 am #15047

    I confirm a bug in the time rules evaluation in 6.0.0-6.0.2 , to fix it , modify the rc.conf manually and add a # before the ? , this must be done for each rule. If your case :

    time_rules = 0#0# 1/ 1/2010/ 7/ 0# 4/ 1/2010/20/59?0#0# 5/ 1/2010/ 7/ 0# 5/ 1/2010/17/ 5?

    becames

    time_rules = 0#0# 1/ 1/2010/ 7/ 0# 4/ 1/2010/20/59?0#0# 5/ 1/2010/ 7/ 0# 5/ 1/2010/17/ 5#?

    Regarding the logon issue, we are not aware of any bug. Could you explain us on what kind of environment are you working ? workgroup/domain ? Also are you logged locally or remotely on the workstation ?

    Time rules will be fixed in 6.0.3

    mdsTutor
    2nd February 2010 at 9:37 pm #15048

    Hello Leonardo

    We are using windows platform and MS Active Directory as domain service. All the users login to the machine physically by using Active Directory domain accounts, not remotely.

    Thanks
    Anders

    Leonardo Bernardini
    12th February 2010 at 11:20 am #15051

    There may be an expection on your policies that prevents our detection routine to find the logged user. IF you get in touch with us directly at vvsupport@vvertex.com , we may send you a simple .exe to run and collect some statistics so we can watch what happens and what to change in 6.0.3 to address your issue,
    Cheers !

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.