Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Canoscan background drivers fill the console log file Apps
I took the advice of one of today's hints and opened the console only to see a line that read:
Looking for devices matching vendor ID=1193 and product ID=8718
marching down the screen. A quick google search later and I was at rentzsch.com, where I found this as part of a discussion of the Canoscan software that comes bundled with Canon scanners (one of which - a LIDE20 - I bought recently):
Two background processes, N067U_ButtonManager and N124U_ButtonManager are started and placed into a boot-time launch folder. N067U_ButtonManager writes "Looking for devices matching vendor ID=1193 and product ID=8717" to system.log once per second. N124U_ButtonManager also writes "Looking for devices matching vendor ID=1193 and product ID=8718." This happens all the time, regardless of whether the scanner is plugged in or not. That means these two processes will write out around 10 megabytes of log files every 24-hour period.
Sure enough, there they were in the Process Viewer, so I killed them. Can't tell if my system is faster, but I sure don't need hundreds of megabytes of useless system logs.

A "find" revealed them at /Library -> CFMSupport -> N124U_ButtonManager. I've moved them to a new "CFMSupport-disabled" folder. I don't know if not having them will affect my use of the scanner; I suspect that they just listen for the convenience buttons (scan, copy, email) that are on the front of the thing. At any rate, I don't use the scanner all that often anyway, so I'll cross that bridge when I come to it.

Thanks to Jonathan 'Wolf' Rentzsch for this valuable advice.
    •    
  • Currently 2.80 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (5 votes cast)
 
[29,611 views]  

Canoscan background drivers fill the console log file | 9 comments | Create New Account
Click here to return to the 'Canoscan background drivers fill the console log file' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Canoscan background drivers fill the console log file
Authored by: displaced on Jun 03, '03 10:43:42AM

I have the same scanner and went though the same thing.

These two 'button managers' are background processes (launched from your user's Login Items settings in System Prefs) which allow you to use the three buttons on the front of the scanner.

The problem is, the drivers support *two* scanner models. The message you're seeing in the console is the driver *not* applicable to your model complaining that it can't find the scanner.

The button manager that *does* work is silent (if you look earlier in the log, you'll see it reports that it's found the proper device).

All you need to do is diable the driver that doesn't apply. I too have the LiDE20. This scanner only needs the N067U_ButtonManager. Disabliong JUST the other file should prevent the messages, and leave you still able to use the buttons.

--
Chris



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: greed on Jun 03, '03 12:32:42PM

I would expect the 'button driver' you do need would log that message if you just happen to not have your scanner on that day.

This continues my belief that hardware vendors have, in fact, little or no idea how to write drivers for their own hardware. It's not just Dazzle.



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: displaced on Jun 03, '03 12:58:52PM

Agreed - if you have the scanner unplugged, the 'correct' driver still logs the message.

This isn't really an issue with the LiDE20, since it is powered entirely from the USB link, so there's no 'turning on' to be done :)

The point's still valid, though. OS X may well be the first time that some vendors have written drivers for a UNIX-alike OS. Conventions like 'Don't spam the console log!' are new to them.

Hopefully, they'll Get A Clue at some point. But I wouldn't hold your breath... :S



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: kevin11 on Oct 12, '03 05:47:29PM
If you are using a TiBook which is frequently disconnected from the Scanner you still get the unwelcome logs. However ther is a freeware Utility by Brian Hill called MacJanitor that is handy for cleaning up useless logs and other system resources. You just have to run it more often than usual (which is not entirely bad anyway)

---
K11

[ Reply to This | # ]

Canoscan under OS X 10.3 anyone?
Authored by: rogerwprice on Nov 25, '03 04:00:33PM

Have you managed to get your Lide 20 working under Panther (10.3)? If so, what is the trick. I have reinstalled but I still get messages about files missing.



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: AdamW on Jun 03, '03 12:47:37PM

After reading this hint, I tried to disable the process not used by my LiDE30. I created a folder called "CFMSupport-disabled" and put into it N124U_Library.shlb and N124U_ButtonManager. Then I restarted. Checked Console and Process Viewer, and saw that the computer was still looking dor a device and the process was running. I dragged "CFMSupport-disabled" out of /Library -> CFMSupport and onto the desktop. Restarted again. Still have the computer looking for a device and the process is still running. So how do I stop the process?



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: displaced on Jun 03, '03 01:01:46PM

In my experience, I didn't actually need to move the files themselves anywhere.

If you look in System Preferences -> Login Items, you should see the two button monitors listed. Simply removing the one you don't need from this list should be enough to prevent the app loading.



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: banditpup on Jun 14, '03 04:54:01AM

i have the LiDE 30. after much trial + error, i found out that there is no need to trash or even move any of the drivers or their preferences.

i was finally able to end my looooonnnng march by removing one of the two drivers from the Login list; unchecking it is not enough to disable the error message. it seems CanoScan will work with *either* driver, but for me, at any rate, the culprit turned out to be the N67U_ButtonManager (8718) and not the N124U_ButtonManager (8717). as soon as i deleted N67U from the Login pane + logged back in, the error line stopped. i guess each of us will have to determine for themselves which driver will work for them.

now i have pretty limited real estate, so i only hook up the scanner when i need it. which means when a scanner can't be found, this console bulls**t starts all over again! since apple obviously prefers that i never turn off the imac, the only solution--short of leaving the scanner plugged in--would be that i manually add the driver back into the Login list only when i use the scanner...

also, it seems the scanner likes to see *both* drivers, because when my scan launches photoshop (in os9, at that!! but that's a whole 'nother gripe...) i get an error message complaining about missing software (worded in a way that is dripping with irony). i just hit 'ok' + everything works just fine. i'd rather live with this than the console madness.

now let's see if canon ever reads my email on this...

---
banditpup



[ Reply to This | # ]
Canoscan background drivers fill the console log file
Authored by: mitra on Nov 15, '03 06:36:12PM

it doesn't look like Canon reads your email, the drivers I downloaded yesterday have this problem.

I disabled the button manager and hope the (intermittently connected) scanner still works, its probably easier to work without the buttons (using File->Aquire or whatever) than dealing with the log-bloat.



[ Reply to This | # ]