Waiting for lock on /dev/null

2007-12-25 8:04:00

Hello sun-managers:

Thank you for all fifteen responses, most of which were bull's-eyes.

Briefly, the problem concerns printcap entries for "dummy" printers,

which had lp=/dev/null, resulting in periodic "waiting for lock on

/dev/null" messages. The solution is to create new null devices for

each dummy printer, and change their printcap lp entries to point to

the new devices. Also, don't use /dev/null for any printers, as this

can result in conflicts with other (non-printer related) software.

Warren Stokes had one of the most succinct answers, and his electrons

probably travelled the farthest, so I will extract from his here:

> From was@lewis.isd.gdwb.OZ.AU Tue Jan 26 14:58:18 1993

> I believe lpd opens the device exclusively (i.e. /dev/null) so all you need

> to do is make a dummy /dev/null device in the spool directory for this

> printer. Try

> mknod /usr/spool/B-1S-11-HALL/nulldev c 3 2

> and then in your printcap:

> :lp=/usr/spool/B-1S-11-HALL/nulldev: etc

> This works for me.

Many thanks to:

Bob Cronin

Actived: 0 answers; - size: 4600 bytes; - view related info - Similar thread

Got something to say?

You must be logged in to post a comment.

thatsjava.com