• Support
  • Articles
  • Resources
  • Products
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead

BUG: LogMeTT Scheduler continues after schedule removed

Moderator: boris

4 postsPage 1 of 1

  LOCKED 
stevo
Newbie

Posts:
19
Joined: Tue Oct 15, 2013 11:08 pm
by stevo » Tue Oct 15, 2013 11:52 pm
Hi Boris,
Thanks a lot for LTT. Very useful. I use it every day...but I think I may have found a bug in the schedule code.

I created an LTT script (hierarchical) with multiple host ('leaf') nodes.
I applied a schedule to only one node.
I restarted as directed in help, and it started executing accordingly.
I then removed the schedule settings and restarted, but it keeps executing per the schedule.
I rebooted the system even, and it still executes.

The schedule only runs when that specific LTT script is open. If I open a different LTT script file, it stops.
The command line syntax according to Sysinternals Process Explorer is:
TTPMACRO /D=<number> C:\Users\<username>\AppData\Local\LogMeTT\Temp_TTL\~macro<N>.ttl /S

This does not match the syntax in the TTPMACRO help, so I can't work out what the "/D=" and "/S" switches do.

I have also tried to identify what the trigger is using Sysinternals Process Monitor, but can't work it out.

I suspect that LogMeTT has somehow written to cache or the registry the command line to run and has not correctly deleted it when the LTT script schedule was removed.

I hope this makes sense.

Thanks,
Stevo.
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Wed Oct 16, 2013 1:29 am
Hi Sveto,

I was not able to reproduce the bug you are describing. Could you please provide more details?

Also, could you tell where in the help file is said that LogMeTT needs to be restarted for the scheduler to work? I am asking, because actually restart is not required. After changing schedule, or any other node related parameter user has to click Apply button and then save LTT file. Saving LTT file forces tray application (that runs scheduler) to re-read the latest saved revision of the file and start, or stop scheduler.

I am not familiar with Sysinternals Process Explorer and cannot comment on the switches it shows.
LogMeTT calls Tera Term with the following parameters:

Full_Path_to_TeraTerm /F=<copy_of_inifile> /M=<macro_file_name> [ /L=<log_file_name>]
Thanks.
Best regards,
Boris
stevo
Newbie

Posts:
19
Joined: Tue Oct 15, 2013 11:08 pm
by stevo » Wed Oct 16, 2013 10:40 pm
Boris,

I MUST CONFESS I HAVE MADE AN ERROR. PLEASE ACCEPT MY SINCERE APOLOGIES.
There is no BUG here. Your code works exactly as you said it does...

I am so sorry for wasting your time.

In my quest to keep copies of all script trees under a "DEPRECATED" top level node for internal script version control, I found that I had kept a copy of the node I thought was executing according to a schedule, and the copy still had the schedule enabled. This was the node that was executing on a schedule, not the latest node.

I have disabled it and the execution has ceased. Yay!

Once again, sorry for any inconvenience, and thank you very much for your kind input.

All the best,
Stevo.
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Thu Oct 17, 2013 12:16 am
No problem :smile: I am glad you found the cause.
Thanks.
Best regards,
Boris
Display posts from previous:
Sort by:
  LOCKED 

4 postsPage 1 of 1

Users browsing this forum: No registered users
cron