Closed GoogleCodeExporter closed 8 years ago
This is tricky to do, and although it was originally implemented it was removed
for the sake of security.
It's not wise to allow a user to control where a file will be written on a
remote devices filesystem.
Can you explain the use case some more, maybe there is a more limited way of
implementing it.
Cheers,
Original comment by leon.j.w...@gmail.com
on 1 Jul 2011 at 8:38
I probably did this the wrong way around, what may be more applicable is to use
the "fetch" action, however allow that "fetch" action to be queued on the
sensor. The problem we had, in our scenario, we fetch pcap for each event
automatically, there is no user interaction, so if we have a steady bout of
hits over a short period, using the fetch action would create many parallel
requests on the sensor, thus maxing the resources. The queue action remedies
this somewhat, and it was easier to patch the code to zip up the results by
jumping to the relevant piece of code. HTH
Original comment by matt.new...@gmail.com
on 1 Jul 2011 at 9:08
You can of course specify a location to save "stored" files in the openfpc.conf
file.
Closing to clean things up.
Original comment by leon.j.w...@gmail.com
on 3 Oct 2012 at 9:16
Original issue reported on code.google.com by
matt.new...@gmail.com
on 13 May 2011 at 3:17