It is possible that the Move to... and Copy to... commands can be configured so that when they operate on a message that is part of a thread, that only that message will be moved, instead of the whole thread?

	reload)
		# Do nothing since ELOG daemon responds to 
		# the changes in conffile directly.
		;;

    reload)
        if [ -f $PIDFILE ]; then
            echo -n "$DESC to reread config file ... "
            kill -HUP `cat "$PIDFILE"`
            echo "done"
        else
            echo "No $PIDFILE found!"
        fi
        ;;

Since elog is only the web server providing (comfortable) access to the logbook database, it relies on the web browser (possibly enhanced by script code) for facilities to attach pictures and other files to entries. So unless your browser has such an extension or someone writes some sort of script that can do it, the only way is to use an external capturing program, save the picture and upload it in the usual way. Cf. also entry 66004.

You could write a script/program that calls the ELOG client with the necessary attributes to submit the entry (see the user's guide).

Did you consider using the "Restrict edit time" option? It should provide the necessary functionality, as long as you don't want to lock the entry at a fixed absolute time, but really only x hours after creation (also, as you talked about closing the "thread" automatically, there is no option to prevent replies after a certain amount of time).

See the administrator's guide.

[code]

[ilcode]

<code>

<pre>