Home / user-386179

3kstc's questions

Martin Hope
3kstc
Asked: 2018-09-26 16:40:08 +0800 CST
  • 3

Brief:

I have a directory where files are dropped arbitrarily in server A. I want to dump these files into server B and delete them from server A.

Background:

I would like write an Bash script where the code iterates through each file, puts the file across to server B, and deletes it straight after. This will be ammended to the cron and called hourly to scrape the files across to server B

Code:

The code I have attempted is:

#!/bin/bash

MY_SCRIPT_NAME=`basename "$0"`
PATH_TO_METRICS='/home/some/directory'

if pidof -o %PPID -x $MY_SCRIPT_NAME > /dev/null; then
    echo "$MY_SCRIPT_NAME already running; exiting"
    exit 1
fi

sftp -i my_priv_key -oPort=12345 [email protected] <<EndOfTransfer
cd $PATH_TO_METRICS
for filename in $PATH_TO_METRICS; do
   PUT "$filename"
   rm "$filename"
done

EndOfTransfer

Relevant Research:

Question:

How does one iterate through files in a given a directory and use sftp to put each of the files across to another server, and delete the file if a successful transfer has happened?

bash sftp
Martin Hope
3kstc
Asked: 2015-03-25 18:43:26 +0800 CST
  • 7

I've got an init.d script which I want it to work in the background, even when I quit from the terminal. However I've tried making it run in the background with nohup but had "no hope", because when I quit, by looking at the pstree I can see the PID disappears and thus nohup stops working.

Q: Is there another apart from nohup way of pushing a script that works in the foreground to the background, even after you quit the terminal?

nohup
Martin Hope
3kstc
Asked: 2015-03-24 17:28:03 +0800 CST
  • 1

I have written up a Shell init.d script named "My_first_initd_script". The script works great when I run it from the /etc/init.d/ -working in the foreground.

I would like to make"My_first_initd_script" script work in the background [daemon] as well so that it works when I quit from the terminal. It's been advised that I need to write up a upstart script. I've read it a dozen times, I don't understand it.

Q: Do I really need an upstart script, if so where do I place the script, and what do I write in the script? Also is there alternative ways?

upstart
Martin Hope
3kstc
Asked: 2015-03-09 19:29:55 +0800 CST
  • 0

The filtered out data from a MQTT live stream is dumped into a csv file named mqtt.csv and the dumping process is done by executor_start_up_job.txt which is written in BASH (has a shebang).

I want to make the dumping of the filter daemon, i.e. in the background, and also want to make it in so that every time the system is rebooted it is done automatically. So I've concluded to write an init.d script, and contents of my code is:

#!/bin/bash
set -x

requested_command=$1

start() {

        /home/ed/start_up_job/executor_start_up_job.txt &
}
# Restart the Dump
stop() {

        killproc executor_start_up_job.txt
        echo
}
### main logic ###
case $requested_command in
  start)
        start
        ;;
  stop)
        stop
        ;;
  status)
        last_line=`cat mqtt.csv | tail -1`
        echo "last print line: $last_line"
        ;;
  restart)
        stop
        start
        ;;
  *)
        echo "Usage: $0 {start|stop|restart|status}"
        exit 1
        ;;
esac
exit 0

Once I have inserted set -x I get the following output:

+ ./MySQL_table_update_daemon.sh start
+ requested_command=start
+ start
+ exit 0

Q: If I can make this code to work, then I will place it into the /etc/init.d/ directory, so that it can work every time. However currently it does not work and the output without the set -x the is nothing i.e it's as if I've just pushed enter in the terminal.

bash