Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. What .conf parameters support '%t' notation, possible feature
request... (Z4)
----------------------------------------------------------------------
Message: 1
Date: Sat, 17 Aug 2019 17:15:55 -0700
From: Z4 <[email protected]>
To: Motion discussion list <[email protected]>
Subject: [Motion-user] What .conf parameters support '%t' notation,
possible feature request...
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Wouldn't it be nice to simply be able to 'cp camera1.conf camera2.conf'
and if they had these settings, no further edits would be necessary:
camera_id = %t
stream_port 'X + %t' # or equivalent
netcam_url rtsp://camera%t/some_path...
then the dynamic %t parameter would take care of differences between the
files, and assuming that the /etc/motion/conf.d/ directory were read in
a consistent order (alphabetical?),then no edits would be necessary to
any of the cameraX.conf files.
Its a minor convenience issue, but adding/removing cameras would be more
streamlined for cases where there are multiple cameras of the same type.
I know the camera_id parameter already supports %t, but I see
'.../camera2.conf' being read before '.../camera1.conf', so that's a bit
unexpected. Otherwise, the code is already present, just may need to be
implemented for a few more parameters.
Can this be done already?
If not, maybe one of the devs. here could point me at the file/directory
to start with and I'll make the changes and provide a patch.
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 158, Issue 29
********************************************
