- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

the_wolverine
Champion
06-29-2010
05:32 PM
1 Solution
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

the_wolverine
Champion
06-29-2010
05:34 PM
By default, even CLI-initiated searches are assigned a Job id. Unfortunately, these disappear immediately upcome completion of the search run. To make the Job id persist you can add '-detach true' to your search:
[/opt/splunk/bin] ./splunk search "search terms" -maxout 100000 -detach true
Job id: 1277828645.277
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

the_wolverine
Champion
06-29-2010
05:34 PM
By default, even CLI-initiated searches are assigned a Job id. Unfortunately, these disappear immediately upcome completion of the search run. To make the Job id persist you can add '-detach true' to your search:
[/opt/splunk/bin] ./splunk search "search terms" -maxout 100000 -detach true
Job id: 1277828645.277
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
bwooden

Splunk Employee
06-29-2010
11:15 PM
It showed in my jobs manager on Splunk 4.1 (build 77833)
