Deployment Architecture

Scripted Input - Script calling another script

jamesvz84
Communicator

I have a scripted input, top20.sh, calling another script - top.sh.

inputs.conf

[script://./bin/top20.sh]
interval = 60
sourcetype = top
source = top
index = linux
disabled = 0

top20.sh:

#!/bin/sh
./bin/top.sh | head -n 20

I am not getting data. Running top.sh works fine. Am I assuming the correct relative path? Any other reasons why this is not returning data?

Tags (3)
0 Karma
1 Solution

jamesvz84
Communicator

The following worked on top20.sh. Not 100% sure, but I believe the modification gets the path of the calling script:

#!/bin/sh
`dirname $0`/top.sh | head -n 20

View solution in original post

jamesvz84
Communicator

The following worked on top20.sh. Not 100% sure, but I believe the modification gets the path of the calling script:

#!/bin/sh
`dirname $0`/top.sh | head -n 20

Ayn
Legend

No, the script will actually be run with the filesystem root (/) as its working directory, so you'd have to provide the full path to your other script in order to execute it successfully.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Reuse: Word-play

This puzzle series (first published here) is based on analysing words.Some of the statements in your puzzle ...

Tuning Edge Processor in Hybrid Mode: What Limits Each Data Path

When you run Edge Processor in hybrid mode, alongside a Splunk heavy forwarder on the same host, two questions ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...