Earlier, I posted the script for wget that I use for this very purpose. From the man page:
 
       GNU Wget is a free utility for non-interactive download of files from
       the Web.  It supports HTTP, HTTPS, and FTP protocols, as well as
       retrieval through HTTP proxies.

       Wget is non-interactive, meaning that it can work in the background,
       while the user is not logged on.  This allows you to start a retrieval
       and disconnect from the system, letting Wget finish the work.  By
       contrast, most of the Web browsers require constant user's presence,
       which can be a great hindrance when transferring a lot of data.

So, it can act like a command line browser. Since the motion control process using simple http, you can hard code wget commands to control motion just like you were using a browser.

Here is the code I use to pause motion detection:

      HOST=`hostname`    
      echo "Pausing motion detection on $HOST"
      /usr/bin/wget -nv -o WGETLOG http://$HOST:8080/0/detection/pause 

Substitute HOST, port and thread as appropriate. Point your browser to the motion control daemon and copy and paste the URL into your script.

You could have cron run this on a regular basis in case your system restarts while you are gone.

This pauses motion detection for this thread altogether (as opposed to having motion continually doing a lot of work only to produce no images). Over the course of your vacation, you might save 3 cents worth of electricity......



From: Jason Sauders <jasauders@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Sent: Sunday, September 2, 2012 12:13:44 PM
Subject: Re: [Motion-user] Camera attached to Motion, yet not wanting it to record. Optimal workaround?

Ah I must have misunderstood. I'm not following how wget or something would take down that camera in question. At any rate, the full blown 100% mask or the high sensitivity rate for motion sounds like it may do the job as well. Appreciate the insight! 

On Sun, Sep 2, 2012 at 5:15 AM, Joerg WEBER <motion@alcatraz.shacknet.nu> wrote:
Jason,

ok, missed that point. You can pause a single thread using the built in
web interface. wget or something simmilar can do this job in a script.


Brgds Joerg.


--


Jason Sauders wrote:
But that would be all or nothing, no? I want all cameras to record except
one in specific.

Thanks!
-J

On Sat, Sep 1, 2012 at 4:56 AM, Joerg WEBER
<motion@alcatraz.shacknet.nu>wrote:

> Jason,
>
>
> if you're using the latest SVN code, you can run motion with a
> commandline switch to disable detection at startup: -m
>
>
> Brgds Joerg.
>
>
>
> --
>
>
>
> Jason Sauders wrote:
> I have a random indoor wireless camera that sometimes I plug in and leave
> on the fireplace mantle when we're away, mostly to use as a dog babysitter
>  since we're at the point where we're starting to trust him a bit more
> out and about. My goal is to have all of my cameras attached to Motion
> since Motion, of course, does some awesome motion based recording. The
> only issue is, I don't want this camera doing any sort of recording. I
> just want it for viewing. I do however have a web page I whipped up (some
> of you may remember this discussion last week... I actually added some
> info to the FAQ page here<
> http://www.lavrsen.dk/foswiki/bin/view/Motion/FrequentlyAskedQuestions#Ho
> w_do_I_see_more_than_one_camera_stream_at_a_time_63
>> ...

>
> But in that particular instance, I'm going against the grain with not
> wanting Motion to do recording. The only thing I can think of is
> incorporating a 100% solid black mask so nothing can ever trigger motion.
>  But I got to wondering, is there a way to adjust the thread.conf file of
>  that camera to enforce no recording whatsoever? Or is the mask the
> optimal solution?
>
> Thanks guys!
>