PacketFence - BTS - PacketFence
View Issue Details
0000817PacketFencepublic2009-10-21 14:402009-10-26 09:46
obilodeau 
obilodeau 
normalminorhave not tried
closedno change required 
 
 
0000817: Nessus scheduled scans
pfcmd schedule add doesn't work, it returns the parameters like if it didn't recognize inputs:

[root@pf-dev pf]# bin/pfcmd schedule add 192.168.1.104 date="0 3 * * *"
Usage: pfcmd schedule <view|add|edit|delete> [number|ip-range|ipaddress/cidr] [assignments]

use nessus to scan ip(s). IP address can be specified as IP, Start-EndIP, IP/xx Cidr format.

examples:
  pfcmd schedule view all
  pfcmd schedule view 1
  pfcmd schedule now 128.11.23.2/24 tid=11808;11835;11890;12209
  pfcmd schedule add 128.11.23.7/24 tid=all,date="0 3 * * *"
  pfcmd schedule add 128.11.23.2/24 tid=11808;11835;11890;12209,date="0 3 * * *"
  pfcmd schedule delete 2

Additionally, documentation is not correct: now not mentioned in possible keywords
No tags attached.
Issue History
2009-10-21 14:40obilodeauNew Issue
2009-10-21 14:40obilodeauStatusnew => assigned
2009-10-21 14:40obilodeauAssigned To => obilodeau
2009-10-21 14:44obilodeauNote Added: 0001357
2009-10-21 14:56obilodeauNote Added: 0001358
2009-10-21 15:17obilodeauNote Added: 0001359
2009-10-21 15:17obilodeauStatusassigned => closed
2009-10-21 15:17obilodeauResolutionopen => no change required
2009-10-26 09:46obilodeauCategoryfuture => 1.8.5

Notes
(0001357)
obilodeau   
2009-10-21 14:44   
I fixed the doc but still need to figure out what's wrong with schedule add.
(0001358)
obilodeau   
2009-10-21 14:56   
Ok, well it seems that it works if I'm careful about escaping:
bin/pfcmd 'schedule add 192.168.1.1-254 date="0 3 * * *"'
(0001359)
obilodeau   
2009-10-21 15:17   
invalid