Synchronization is taking too long after reboot.

[gforti84]

Hello. The synchronization is taking too long after I reboot the system. My sync dir is in a mounted HDD, I have changed the .config file as below:

sync_dir = "~/HD-DATA/OneDrive/"  
sync_dir_permissions = "700"  
sync_file_permissions = "600"  

[abraunegg]

@gforti84
Can you help define 'takes too long' ?

What is your application version? What is the output of onedrive --version

What is your full configuration? What is the output of onedrive --display-config

[gforti84]

Hello,

The second time I run it, it takes about 2m30s. The first time is >15 min

Version: onedrive v2.4.25-1+np1
Full config:

Configuration file successfully loaded
onedrive version                             = v2.4.25-1+np1
Config path                                  = /home/forti/.config/onedrive
Config file found in config path             = true
Config option 'sync_dir'                     = /home/forti/HD-DATA/OneDrive/
Config option 'enable_logging'               = false
Config option 'log_dir'                      = /home/forti/.config/onedrive/log/
Config option 'disable_notifications'        = false
Config option 'min_notify_changes'           = 5
Config option 'skip_dir'                     = 
Config option 'skip_dir_strict_match'        = false
Config option 'skip_file'                    = ~*|.~*|*.tmp
Config option 'skip_dotfiles'                = false
Config option 'skip_symlinks'                = false
Config option 'monitor_interval'             = 300
Config option 'monitor_log_frequency'        = 6
Config option 'monitor_fullscan_frequency'   = 12
Config option 'read_only_auth_scope'         = false
Config option 'dry_run'                      = false
Config option 'upload_only'                  = false
Config option 'download_only'                = false
Config option 'local_first'                  = false
Config option 'check_nosync'                 = true
Config option 'check_nomount'                = false
Config option 'resync'                       = false
Config option 'resync_auth'                  = false
Config option 'cleanup_local_files'          = false
Config option 'classify_as_big_delete'       = 1000
Config option 'disable_upload_validation'    = false
Config option 'bypass_data_preservation'     = false
Config option 'no_remote_delete'             = false
Config option 'remove_source_files'          = false
Config option 'sync_dir_permissions'         = 700
Config option 'sync_file_permissions'        = 600
Config option 'space_reservation'            = 52428800
Config option 'application_id'               = 
Config option 'azure_ad_endpoint'            = 
Config option 'azure_tenant_id'              = common
Config option 'user_agent'                   = 
Config option 'force_http_11'                = false
Config option 'debug_https'                  = false
Config option 'rate_limit'                   = 0
Config option 'operation_timeout'            = 3600
Config option 'dns_timeout'                  = 60
Config option 'connect_timeout'              = 10
Config option 'data_timeout'                 = 600
Config option 'ip_protocol_version'          = 0
Config option 'sync_root_files'              = false
Selective sync 'sync_list' configured        = false
Config option 'sync_business_shared_folders' = false
Business Shared Folders configured           = false
Config option 'webhook_enabled'              = false

[abraunegg]

@gforti84
Just as an FYI - please use 3 x backticks to post code / application output

[abraunegg]

@gforti84
For that application version your experience is 100% normal.

The reason for this is the way that application version handles startup processing.

This is dramatically changed with v2.5.0 which is in heavy development. Please read #2478 for details.

[gforti84]

Ok. Thanks for your response.