> I see what happened. After figuring out how to query the db (never > worked with sqlite before) a task I had in my trash can ended up getting > tied to this new schedule I added. This resulted in the issue.
Surprised that this could actually happen. Note that there's a second column in the tasks table, schedule_location, which indicates whether the schedule is in schedules or schedules_trash. > May be a good thing to disassociate items that are in the Trashcan from > ever being activated as far as schedules and tasks go. Once they are in > the trash, they should be completely disabled (imho) Yes, trashcan tasks should never run. I've committed r13615 to prevent the scheduling mechanism from doing this. Should be in the next release. -- Greenbone Networks GmbH Neuer Graben 17, 49074 Osnabrueck, Germany | AG Osnabrueck, HR B 202460 Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
