Page 1 of 1

NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 27 Jul 2015 18:26
by Southcross
w/ full Install of v10 on a hard drive...

I am trying to set up a CUPS server, with CUPS-PDF to act as a virtual print server for our offices to "print" directly from applications to a PDF for the printing department. I have SMB configured with a share to hold the files, CUPS installed using this writeup (viewtopic.php?f=72&t=8512&p=52323&hilit=CUPS#p52323), and CUPS-PDF installed.

Following the HowTo it appears that a few things have changed with v10, "devfs" to "devd" appears to be one of them? also, it appears that some settings are not saving? I manually added a [Printers] section to smbd.conf (I think that was the file? LOL). If I restart the service printers appear on the network share, but reboot the machine and the config file reverts and I lose all my changes :(

I can't get CUPS to "share" printers... and I think it has something to do with the changes to v10 and the fact I can't save a custom SMB config?

Also, I notice that files are being saved with -rw------- permissions, I need to change that to read & write for everyone. I "think" I know how to fix that with "create mask", but I am just still trying to figure out the problem with sharing first

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 28 Jul 2015 16:43
by Southcross
suggestions? the SMB/CUPS/CUP-PDF combo seems like a simple solution for network print submission...

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 30 Jul 2015 10:40
by ChriZathens
If you are using embedded, then the smb.conf file cannot be preserved across reboots.
Add the additional printers section in Services|CIFS/SMB|Settings -->Advanced settings, Auxiliary parameters section and see if it works.

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 30 Jul 2015 15:10
by Southcross
I performed a "full install" using a live USB, shouldn't it then keep my changes?

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 30 Jul 2015 16:07
by ChriZathens
I am not 100% sure, because I haven't used full install in a veeeeery long time... apologies.
Please wait for someone else to confirm, or you can try the Auxiliary parameters I posted above and post the outcome

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 30 Jul 2015 18:25
by Southcross
I'll give it a shot, but it looks like the "Auxiliary" section is just for adding parameters/options to the [Global] section of the SMB config file...

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 11 Aug 2015 17:03
by Southcross
OK... so... it appears that Samba was precompiled for N4F without CUPS support? (following the instructions located here: https://wiki.samba.org/index.php/Samba_ ... int_server )

Code: Select all

smbd -b | grep CUPS
do I just "re-install" SMB with CUPS support added, or do I need to do anything special to not break N4F, or am I SOL? I could go to a vanilla *nix install, but I much rather use the N4F interface :/

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 14 Aug 2015 16:45
by Southcross
thoughts/suggestions?

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 15 Aug 2015 11:00
by ChriZathens
Really not sure. Perhaps the devs can help - please bring it to their attention.
Filing an issue on SourceForge is a good idea.
A Google search revealed that in rc.conf you must add

Code: Select all

cupsd_enable="YES"
Have you tried ?

Sorry for being laconic - I am from mobile.

Re: NAS4free v10 as a SMB/CUPS/'Print to PDF' server

Posted: 24 Aug 2015 22:05
by Southcross
ChriZathens wrote:Really not sure. Perhaps the devs can help - please bring it to their attention.
Filing an issue on SourceForge is a good idea.
A Google search revealed that in rc.conf you must add

Code: Select all

cupsd_enable="YES"
Have you tried ?

Sorry for being laconic - I am from mobile.
woops... I thought I replied already to this? yes, I already have it set to "YES". I have been going in circles over this and I think it has entirely to do with the inability to edit the SMBD.conf file directly.