I have modified the scripts slightly based on recommendations on this thread. But this still does not work. I am just looking for mbsync to run every two minutes. What do most people use?
It is crazy that something so obvious should be so difficult to get right. Vikas --- # mbsync.service [Unit] Description=Mbsync synchronization service [Service] Type=oneshot ExecStart= /usr/local/bin/mbsync -V daily #ExecStartPost=/bin/sh -c '/usr/bin/notmuch new && /home/vikas/bin/afew -t -n && /home/vikas/bin/afew --move-mails -v && echo "notmuch `date`" >> /home/vikas/bin/maillog.log' [Install] WantedBy=default.target #mbsync.timer [Unit] Description=Mysync synchronization timer [Timer] OnBootSec=2m OnUnitActiveSec=2m Unit=mbsync.service [Install] WantedBy=timers.target On Fri, 15 Jul 2022 at 13:36, Max Gautier <ashelia1...@gmail.com> wrote: > Check the status for both the timer and the service, but on the top of > my head: > > [Service] > > ... > > ExecStartPost=/bin/sh -c 'notmuch new && afew -t -n && afew --move-mails > -v > > && echo "notmuch `date`" >> ~/tmp/maillog.log' > > I had problems in the past when breaking Exec lines on several lines, > might be the reason it does not work. > > > [Timer] > > OnBootSec=2m > > OnCalendar=*:00/2 > That does not seem to conform to the format in systemd.time(7) ? You can > just use 'daily' (inferring from your channel name) > > > Unit=mbsync.service > > That's not needed, the default is to trigger the service with matching > unsuffixed name > > -- > Max Gautier >
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
