GPhoto keep randomly removing filename entry from setting file

Paul Hardwick <[email protected]>
Newsgroups gmane.comp.multimedia.gphoto.user
Message-ID <CAC7ayAxYLoBQsK0LzkWZi8MTSU_upqAsqsDMihux3Fz-zfuk6g@mail.gmail.com>
We have been using Photo successfully for a while to control some Nikon
D7200 cameras. We have recently upgraded the functionality of two of our
stations and started receiving a weird symptom. For some reason the
*filename* entry keeps getting removed from our gphoto settings file. It
will work fine for a few hours and then all of a sudden we start getting a
log entry saying *'Could not claim the USB device'* Given all the standard
causes for this error aren't valid we dug further and found that our
settings file had been changed. For some reason the *filename* entry which
had been there is now missing.

I know the setting file can get edited to update camera and USB port
details, but have no ideas why the *filename* entry is being removed. I
have the good version of the setting file included below ( actual filename
modified to remove client name). We have filename as the last line, is
there maybe some positional requirement I missed?

Thanks for your help,
Paul

cat /root/.gphoto/settings

gphoto2=model=Nikon DSC D7200
> gphoto2=port=usb:001,004
> libgphoto=cached-images=2
>
> gphoto2=filename=/home/pi/Desktop/name-client/client/img/fileprefix-20%y_%m_%d-T%02n_%H_%M_%S.%C


Config

This version of gphoto2 is using the following software versions and
> options:
> gphoto2         2.5.15         gcc, popt(m), exif, no cdk, no aa, no jpeg,
> readline
> libgphoto2      2.5.15         all camlibs, gcc, ltdl, EXIF
> libgphoto2_port 0.12.0         iolibs: disk ptpip serial usb1
> usbdiskdirect usbscsi, gcc, ltdl, USB, serial without locking


We are running under Rasperian on a Pi 3B

_______________________________________________
Gphoto-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gphoto-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.