Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Terminal Error: Unable to read "/private/etc/cups/cups-files.conf" due to errors.

After finding out that my Kodak ESP C310 printer was no longer printing after installing OS X Yosemite, I tried entering these into the terminal to get the driver working again.

sudo sh -c 'echo "Sandboxing Relaxed" >> /etc/cups/cups-files.conf'

sudo launchctl stop org.cups.cupsd

Nothing happened the first time I tried it, so I tried it again with still no luck. Now within seconds of opening the terminal I get this message :

" /private/etc/cups/cups-files.conf"

It pops up every few seconds, so it is practically impossible for me to type anything into the terminal without it popping up right in the middle. I tried the fix from the other discussion on this issue, and that didn't work. also I'm noticing that my printer isn't even added under "printers and scanners" anymore. I tried to re-add it, but I cannot without a driver that functions with 10.10.1

Any suggestions on how I should deal with this?

Mac Pro, OS X Yosemite (10.10.1)

Posted on Dec 6, 2014 6:36 PM

Reply
6 replies

Dec 6, 2014 10:25 PM in response to btothec1221

Back up all data.

Select

Shell ▹ New Command

from the Terminal menu bar. Uncheck the box marked

Run command inside a shell

if checked.

Copy and paste the following line into the text box that opens, then press return:

mkdir disabled_shell_files

Close the Terminal window that opens. Repeat with this line:

mv .profile .bash_history .bash_profile .bashrc .inputrc disabled_shell_files

Your old shell initialization and history files will be saved in a directory named "disabled_shell_files" at the top level of your home directory. It's normal that some of these files will not exist, and therefore you will get some "no such file" errors.

Close the window, open a new one, and test.

Dec 7, 2014 1:09 PM in response to Linc Davis

Thanks for the response, but unfortunately this did not work. I followed the instructions, and even as I was working in the text box and had the other terminal window open, the message was still being created in the first terminal window. After closing everything and opening a new one, I still get this:


Broadcast Message from root@MacBook-Pro.local

(no tty) at 16:06 EST...

Unable to read "/private/etc/cups/cups-files.conf" due to errors.

I was able to locate the "disabled_shell_files" folder and it was absolutely empty, if that information helps at all.

Any other suggestions?

Dec 7, 2014 1:47 PM in response to btothec1221

The permissions and ownership on /private/etc/cups/cups-files.conf should be:

/bin/ls -leO@ /private/etc/cups/cups-files.conf

-rw-r--r-- 1 root _lp compressed 3297 Mar 8 2014 /private/etc/cups/cups-files.conf


See "man cups-files" for the format of the cups-files.conf file



The contents of the /private/etc/cups/cups-files.conf file should look like:

#

# "$Id: cups-files.conf.in 11203 2013-07-26 21:32:33Z msweet $"

#

# Sample file/directory/user/group configuration file for the CUPS scheduler.

# See "man cups-files.conf" for a complete description of this file.

#


# List of events that are considered fatal errors for the scheduler...

#FatalErrors config


# Do we call fsync() after writing configuration or status files?

#SyncOnClose No


# Default user and group for filters/backends/helper programs; this cannot be

# any user or group that resolves to ID 0 for security reasons...

#User _lp

#Group _lp


# Administrator user group, used to match @SYSTEM in cupsd.conf policy rules...

SystemGroup admin

SystemGroupAuthKey system.print.admin


# User that is substituted for unauthenticated (remote) root accesses...

#RemoteRoot remroot


# Do we allow file: device URIs other than to /dev/null?

#FileDevice No


# Permissions for configuration and log files...

#ConfigFilePerm 0644

#LogFilePerm 0644


# Location of the file logging all access to the scheduler; may be the name

# "syslog". If not an absolute path, the value of ServerRoot is used as the

# root directory. Also see the "AccessLogLevel" directive in cupsd.conf.

AccessLog /private/var/log/cups/access_log


# Location of cache files used by the scheduler...

#CacheDir /private/var/spool/cups/cache


# Location of data files used by the scheduler...

#DataDir /usr/share/cups


# Location of the static web content served by the scheduler...

#DocumentRoot /usr/share/doc/cups


# Location of the file logging all messages produced by the scheduler and any

# helper programs; may be the name "syslog". If not an absolute path, the value

# of ServerRoot is used as the root directory. Also see the "LogLevel"

# directive in cupsd.conf.

ErrorLog /private/var/log/cups/error_log


# Location of fonts used by older print filters...

#FontPath /usr/share/cups/fonts


# Location of LPD configuration

#LPDConfigFile launchd:///System/Library/LaunchDaemons/org.cups.cups-lpd.plist


# Location of the file logging all pages printed by the scheduler and any

# helper programs; may be the name "syslog". If not an absolute path, the value

# of ServerRoot is used as the root directory. Also see the "PageLogFormat"

# directive in cupsd.conf.

PageLog /private/var/log/cups/page_log


# Location of the file listing all of the local printers...

#Printcap /Library/Preferences/org.cups.printers.plist


# Format of the Printcap file...

#PrintcapFormat bsd

#PrintcapFormat plist

#PrintcapFormat solaris


# Location of all spool files...

#RequestRoot /private/var/spool/cups


# Location of helper programs...

#ServerBin /usr/libexec/cups


# SSL/TLS certificate for the scheduler...

#ServerCertificate /Library/Keychains/System.keychain


# SSL/TLS private key for the scheduler...

#ServerKey


# Location of other configuration files...

#ServerRoot /private/etc/cups


# Location of Samba configuration file...

#SMBConfigFile


# Location of scheduler state files...

#StateDir /private/etc/cups


# Location of scheduler/helper temporary files. This directory is emptied on

# scheduler startup and cannot be one of the standard (public) temporary

# directory locations for security reasons...

#TempDir /private/var/spool/cups/tmp


#

# End of "$Id: cups-files.conf.in 11203 2013-07-26 21:32:33Z msweet $".

#

Jan 5, 2015 10:14 AM in response to btothec1221

I had the same problem. After updating to Yosemite, I could not print to my Dell 2130 cn anymore and tried to fix it with various suggestions found online, when I hit this error message (I added "Relax Sandboxing" as suggested, but introduced a typo). Luckily, I found in this very directory a "cups-files.con.pre-update" and copied that back to the original (using sudo). and the error was gone.


In order to get my printer working again I used the steps suggested here and the Yosemite fix here. Thanks for your help, Chris and UoL Computing Servies!



Best wishes

Tom

Jan 5, 2015 5:17 PM in response to btothec1221

I've been a windows user longer than I have been a Mac user, so a lot of the ins and outs of these machines are still really confusing to me. I tried a lot of the suggestions, but didn't have any luck. I simply re-downloaded Yosemite and hoped it would correct the terminal error. It worked! No more error! The printer still was not working. I found this discussionand downloaded the kodak file listed. It wasn't the one for my exact printer, but somehow the machines are communicating again. I had to change the security settings a bit to allow the download from outside the app store. Everything is running smoothly now!

Thanks for the help!

Terminal Error: Unable to read "/private/etc/cups/cups-files.conf" due to errors.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.