<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>137981</bug_id>
          
          <creation_ts>2006-06-25 15:42 0000</creation_ts>
          <short_desc>keychain --lockwait 0 does not have expected behaviour</short_desc>
          <delta_ts>2006-09-08 14:39:33 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>furlongm@gmail.com</reporter>
          <assigned_to>agriffis@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>furlongm@gmail.com</who>
            <bug_when>2006-06-25 15:42:08 0000</bug_when>
            <thetext>I usually start my KDE session with one konsole but with around ten tabs open on it. I only want keychain output to come up on one so looking at the options, I saw the --lockwait option.

   --lockwait seconds
       How long to wait for the lock to become available. Defaults to 30 seconds.

If it is locked I don&apos;t want to bother waiting at all, so I set lockwait to 0, meaning wait zero seconds, don&apos;t wait at all. 

After a few unsucessful attempts (an infinite loop waiting for the lock), a quick look at the script shows that using a value of zero for the seconds seems to mean wait indefinitely for the lock, rather than waiting zero seconds. Is this the correct behaviour (as in expected). If so, maybe a comment to this effect in the man page or help output would be appropriate.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>agriffis@gentoo.org</who>
            <bug_when>2006-09-08 14:39:33 0000</bug_when>
            <thetext>Good point.  0 was supposed to mean forever, but it makes more sense to use -1 for that and let 0 return immediately.

Fixed in 2.6.6</thetext>
          </long_desc>
      
    </bug>

</bugzilla>