PiBox

This appears to be a change to the smb command in piboxd, where the "-o <options>" needs to include "vers=1" or "vers=3" or something. It's not clear what it should be but "vers=1" seems to be the fallback for the old default setting (which is no longer set).

Also, or possibly in place of, I can try removing ",sec=ntlm" which is set in piboxd:smb.c in the default command.

"vers=1.0" fixes this problem. At the same time, I'm implementing the option of disabling both SMB and stream handling in piboxd. This will allow piboxd to be more lightweight on systems like Xeon.

Currently need to implement -x option for piboxd's cross.sh, as was done for the launcher, so the build picks up the proper app.cfg file.

Fixes tested, committed and pushed - including metabuild.

Changes seem to work but it's unclear if this fixes the reported issue.

Moving this down the priority list and will recheck again later to see if the problem shows up anymore.

Verified that this problem has been addressed. However, there were additional logs being dumped to syslog on a frequent basis. These have to do with smb thinking it needs to look in /media/usb but that doesn't exist until we stuff a USB stick in the port.

Those messages were filling up /var/log/messages and there is nothing to rotate that yet. So I disabled logging via syslog with

syslog = 0

in smb.conf in the dev platform build. This moved the messages to /var/log/samba/smbd.log, which is rotated at 50k.

Tested, committed and pushed.

Closing issue.