Thanks for your response, it works fine. I read in /etc/default/voyage-util: "Apart from /var/tmp and /var/log, add extra directories to allow read-write." As I understand I don't need the variable $VOYAGE_SYNC_DIRS? Or what means this variable?
Niels Am 17.01.2014 02:38, schrieb Kim-man 'Punky' TSE: > Hi Niels, > > Locate your printer spool directory (/var/spool/<whatever>) and other > directories that requires RW. Then put the directory name (without > leading "/") to VOYAGE_SYNC_DIRS variable in > /etc/default/voyage-util. For example, Voyage MPD is set with: > > VOYAGE_SYNC_DIRS="$VOYAGE_SYNC_DIRS var/lib/mpd var/lib/alsa" > VOYAGE_SYNC_RECOVER="YES" > VOYAGE_SYNC_RECOVER_DIRS="var/lib/mpd var/lib/alsa" > > Regards, > Punky > > On 1/17/2014 6:13 AM, Niels$ wrote: >> I installed Voyage-Linux V0.9R2 on a Alix-Board and it runs fine. >> Now I installed cups as it comes from Debian and my Alix works as a >> printserver. But only until the next reboot, because after that the CF >> is mounted readonly. Thats a nice idea of Voyage-Linux, but I'm afraid, >> that's for using as print-server not possible. Maybe I can reconfigure >> cups to work on the ramdrive. But I guess that there is not enough RAM >> to handle larger printjobs. In 2nd step I want to use it as >> airprint-server too. Here it has to rendering the information from the >> Apple-device, so the print-job is in 2 different formats to hold on >> drive/RAM. >> Are there any ideas how I can solve this? OK CF everytime RW-mounted... >> At the assumed print-volume not the big problem but I guess, that the >> Linux makes a lot of RW-traffic to in this case? >> >> Niels >> >> _______________________________________________ >> Voyage-linux mailing list >> [email protected] >> http://list.voyage.hk/mailman/listinfo/voyage-linux > > _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
