Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 3 of 3 FirstFirst 123
Results 31 to 36 of 36

Thread: changing/downloading files with permissions

  1. #31
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,614
    Thanks
    2,006
    Thanked 4,947 Times in 3,269 Posts
    Can't understand why you are mucking about with cron jobs when ABM has a built in scheduler. If you want to automatically update the provider file add an option to do it when the plugin runs.
    Help keep OpenViX servers online.Please donate!

  2. The Following User Says Thank You to Huevos For This Useful Post:

    dsayers (27-09-16)

  3. #32
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,761
    Thanks
    473
    Thanked 607 Times in 433 Posts
    Quote Originally Posted by Huevos View Post
    Can't understand why you are mucking about with cron jobs when ABM has a built in scheduler. If you want to automatically update the provider file add an option to do it when the plugin runs.
    The closest I've got to that is having it run the plugin on boot and set a power timer or add an url into main.py
    Last edited by dsayers; 27-09-16 at 16:15.

  4. #33
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,761
    Thanks
    473
    Thanked 607 Times in 433 Posts
    Quote Originally Posted by Huevos View Post
    Can't understand why you are mucking about with cron jobs when ABM has a built in scheduler. If you want to automatically update the provider file add an option to do it when the plugin runs.
    Would this work?

    Code:
     
    import schedule
    import time
    
    def job():
           call('/usr/script/updaProviders.sh')
    
    schedule.every().day.at("00:00").do(job)
    
    I'm not sure if this is needed 
    
    while True:
        schedule.run_pending()
        time.sleep(1)
    Or could I call in the updateproviders.py file?

  5. #34
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,614
    Thanks
    2,006
    Thanked 4,947 Times in 3,269 Posts
    If you want it to run before a scan call it in the _init_ or onFirstExec in main.py. There is already a scheduler so no point recreating the wheel.
    Help keep OpenViX servers online.Please donate!

  6. #35
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,761
    Thanks
    473
    Thanked 607 Times in 433 Posts
    Quote Originally Posted by Huevos View Post
    If you want it to run before a scan call it in the _init_ or onFirstExec in main.py. There is already a scheduler so no point recreating the wheel.
    In autobouqetesmarker? I thought you said not to modify the files in autobouqetesmarker when I mentioned that I managed to add my custom.xml github link to the main.py because updates will overwrite them so to keep it a standalone plugin.

    The above didn't work I got no module named schedule

  7. #36
    dsayers's Avatar
    Title
    ViX Beta Tester
    Join Date
    Mar 2016
    Posts
    1,761
    Thanks
    473
    Thanked 607 Times in 433 Posts
    I was helping someone in another thread and had a thought would I be able to download abm zip do my edits and and rename abm to AutoBouquetsMakerCustomMix and do an IPK? for it that way it wont be overwritten with updates

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.