Author Topic: I set lock time to 0, and it keeps locking out me now  (Read 478 times)

0 Members and 1 Guest are viewing this topic.

Offline dahongfei

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
I set lock time to 0, and it keeps locking out me now
« on: July 22, 2014, 07:17:00 am »
I though 0 is never, but it does mean zero.

Now as soon as I log in, it locks/logs me out.

What do i do?

Offline puppies

  • Hero Member
  • *****
  • Posts: 1660
    • View Profile
  • BitShares: puppies
Re: I set lock time to 0, and it keeps locking out me now
« Reply #1 on: July 22, 2014, 07:38:22 am »
There should be a json file you can manually edit.  What OS are you on?

**edit** there might not be.  If you don't have a backup of the wallet, you might need to open the wallet in the command line interface.  That will allow you to set the logout time.

I would suggest you wait til someone that knows more about this than me answers to do anything drastic.
« Last Edit: July 22, 2014, 07:44:27 am by puppies »
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline testz

Re: I set lock time to 0, and it keeps locking out me now
« Reply #2 on: July 22, 2014, 07:38:54 am »
I though 0 is never, but it does mean zero.

Now as soon as I log in, it locks/logs me out.

What do i do?

Try make it default as described here: https://bitsharestalk.org/index.php?topic=5871.msg78753#msg78753

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12524
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: I set lock time to 0, and it keeps locking out me now
« Reply #3 on: July 22, 2014, 07:40:59 am »
you can take 999999999
but dont take too many
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline testz

Re: I set lock time to 0, and it keeps locking out me now
« Reply #4 on: July 22, 2014, 07:42:45 am »
you can take 999999999
but dont take too many

GUI limit this for 99999999 (3 years+) maybe in json you can put more but I think 3 years it's more then enough  :)