[SOLVED] motion script now runs motion without sudo

sdowney717 · 07-06-2017, 02:23 AM

I was able to figure out the pid file. Simply tell motion to write its pid in my user folder

This script actually works to rename the motion-files folder to one with datetime appended, then creates a new motion-files folder for the motion program to create new jpgs.
It works ok even without killing motion running process.

If I try 'pkill motion', the script terminates at that line.
execute 'pkill motion'in a terminal and it kills motion, just won't work in a script.

How could I kill motion daemon in a script?

Code:

#!/bin/bash
echo "foo"
#pkill motion


mv /home/scott/testmotion/motion-files /home/scott/testmotion/motion-files$(date +%F-%H:%M:%S)
mkdir /home/scott/testmotion/motion-files
motion
echo "foofoo"

datetime descriptors list
https://www.cyberciti.biz/faq/unix-linux-bash-get-time/

scasey · 07-06-2017, 11:41 AM

What is the name of the script?
From man pkill:

Code:

pkill will send the specified signal (by default SIGTERM) to each process

and

Code:

The  process  name  used  for  matching  is limited to the 15 characters present in the output of /proc/pid/stat.

I'm just guessing, of course.

sdowney717 · 07-06-2017, 12:06 PM

Quote:

Originally Posted by scasey

What is the name of the script?
From man pkill:

Code:

pkill will send the specified signal (by default SIGTERM) to each process

and

Code:

The  process  name  used  for  matching  is limited to the 15 characters present in the output of /proc/pid/stat.

I'm just guessing, of course.

But I cant use pkill in the executable script as it kills the script, Terminal echoes back 'terminated' and wont run the rest of the script.

BW-userx · 07-06-2017, 12:10 PM

Quote:

Originally Posted by sdowney717

But I cant use pkill in the executable script as it kills the script, Terminal echoes back 'terminated' and wont run the rest of the script.

go back and take a peek at your other post I left you some goodies
http://www.linuxquestions.org/questi...75#post5731475

scasey · 07-07-2017, 09:16 AM

I'll try one more time. What is the name of the script?

sdowney717 · 07-07-2017, 09:20 AM

Quote:

Originally Posted by scasey

I'll try one more time. What is the name of the script?

Motionsh.sh I wrote it.

scasey · 07-07-2017, 09:25 AM

Quote:

Originally Posted by sdowney717

Motionsh.sh I wrote it.

So, if pkill kills all jobs that match the pattern given as seen in the output of /proc/pid/stat it's just possible that it's killing your
script because of the name.

Try calling it some name that does not include the word "motion," uncomment the pkill line and see if it will run.

Let us know what happens, please.

sdowney717 · 07-07-2017, 09:28 AM

Ok will do this today.

sdowney717 · 07-07-2017, 05:25 PM

Yes, it must have been killing the script due to its name.
I renamed script to mmm.sh, and it runs fine

the script

Code:

#!/bin/bash
echo "foo"
pkill motion
mv /home/scott/testmotion/motion-files /home/scott/testmotion/motion-files$(date +%F-%H:%M:%S)
mkdir /home/scott/testmotion/motion-files
motion
echo "foofoo"

the terminal

Code:

scott@scott-P5QC:~/Desktop$ ./mmm.sh
foo
[17686912] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[17686912] [NTC] [ALL] motion_startup: Motion 3.2.12+git20140228 Started with SDL support
[17686912] [NTC] [ALL] motion_startup: Logging to file (/home/scott/testmotion/motion.log)
foofoo
scott@scott-P5QC:~/Desktop$ ./mmm.sh
foo
[27541888] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[27541888] [NTC] [ALL] motion_startup: Motion 3.2.12+git20140228 Started with SDL support
[27541888] [NTC] [ALL] motion_startup: Logging to file (/home/scott/testmotion/motion.log)
foofoo
scott@scott-P5QC:~/Desktop$ ./mmm.sh
foo
[9867648] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[9867648] [NTC] [ALL] motion_startup: Motion 3.2.12+git20140228 Started with SDL support
[9867648] [NTC] [ALL] motion_startup: Logging to file (/home/scott/testmotion/motion.log)
foofoo
scott@scott-P5QC:~/Desktop$

scasey · 07-07-2017, 06:11 PM

Quote:

Originally Posted by sdowney717

Yes, it must have been killing the script due to its name.
I renamed script to mmm.sh, and it runs fine

Cool! Glad we found the solution.