SCO Openserver 5.0.7 Hung process problem


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers SCO Openserver 5.0.7 Hung process problem
# 1  
SCO Openserver 5.0.7 Hung process problem

Hi guys


I installed this new server with 5.0.7 openserver and i'm getting a lot of this process, if a stop and restart the printer spooler they go away but after a few minutes they appear again.This is how it looks like.


root 372 615 0 - - 00:00:00 <defunct>
root 396 615 0 - - 00:00:00 <defunct>
root 419 615 0 - - 00:00:00 <defunct>
root 444 615 0 - - 00:00:00 <defunct>
root 467 615 0 - - 00:00:00 <defunct>
root 500 615 0 - - 00:00:00 <defunct>
root 528 615 0 - - 00:00:00 <defunct>
root 550 615 0 - - 00:00:00 <defunct>

There are about 15 pages of this process ,

Is there anything we can do to stop this.

thanks a lot
 

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #401
Difficulty: Medium
The 3D printing process builds a three-dimensional object from a computer-aided design (CAD) model.
True or False?

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Need to end Backup Process SCO Openserver 5

I was attempting to run a backup at our business last Friday evening when I apparently locked up our whole mainframe. Rather than observing the current time and adding a minute or two to that for the backup start time (like I typically would), I accidentally entered the actual current time to the... (11 Replies)
Discussion started by: hometrics
11 Replies

2. SCO

SCO Openserver 6 Console Display Problem

I am trying to upgrade our SCO Openserver 6 box to some newer HW. I can get everything working correctly except for the console display. The boot command shows up correctly, as does the SCO Openserver 6 splash screen. Right as the SCO legal ease is displaying the screen suddenly jumps to only... (4 Replies)
Discussion started by: Jim546
4 Replies

3. SCO

SCO OpenServer 5.0.5 Problem

I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system. Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System... (2 Replies)
Discussion started by: jesmith
2 Replies

4. SCO

SCO OpenServer 5.0.7 Installation problem on HP ML310 G4

can not for the life of me workout which BTLD to load allways shows no HDD available can any one give me a clue tried hpsas aacraid lsil a160 a320 server is a ML310 G4 ?????:confused::confused: (7 Replies)
Discussion started by: wildginger
7 Replies

5. SCO

SCO OpenServer 5.0.7 Installation problem

we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached). At the time of installation we link both driver BTLD Boot: Defbootstr link=accraid ad320 Aftes succesfully installation of accraid btld... (6 Replies)
Discussion started by: hafizurr
6 Replies

6. SCO

sco openserver 5.07 installation problem

Hi everyone, We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies

7. UNIX for Dummies Questions & Answers

SCO Openserver 5.0.7 Process table overflow

Hello guys. This is the error that i'm getting , once i get the error i have to turn off my server ( is the only way to get it up and running again). I encreased the size of that table but still getting the same error , is there anything that i can do to stop getting this error. I will... (0 Replies)
Discussion started by: josramon
0 Replies

8. UNIX for Dummies Questions & Answers

RE: login problem with SCO openserver

I am running the beta version of Openserver by SCO and the Graphical login only gives me the option of logging into the system v xwindows and I know that this build included KDE 3.3 I have tried the kde kdm command at shell prompt: command not found. Any ideas anyone? (0 Replies)
Discussion started by: coreykirk
0 Replies

9. UNIX for Dummies Questions & Answers

SCO OpenServer Booting Problem

My company has a Compaq NeoServer running SCO OpenServer Release 5 (vintage late 1998) that we inherited from another small company. This has been a very reliable file server for our small company. We recently installed a new Linux server and would like to convert the NeoServer to other functions... (1 Reply)
Discussion started by: Jeff Boyce
1 Replies

10. Filesystems, Disks and Memory

SCO openserver 5 install problem

Hello all, I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies
lpc(1B) 					     SunOS/BSD Compatibility Package Commands						   lpc(1B)

NAME
lpc - line printer control program SYNOPSIS
/usr/ucb/lpc [ command [ parameter...]] DESCRIPTION
The lpc utility controls the operation of local printers. Use lpc to perform the following functions: o start or stop a printer, o disable or enable a printer's spooling queue, o rearrange the order of jobs in a print queue, or o display the status of a printer print queue and printer daemon. lpc can be run from the command line or interactively. Specifying lpc with the optional command and parameter arguments causes lpc to interpret the first argument as an lpc command, and all other arguments as parameters to that command. Specifying lpc without arguments causes it to run interactively, prompting the user for lpc commands with lpc>. By redirecting the standard input, lpc can read commands from a file. USAGE
lpc commands may be typed in their entirety or abbreviated to an unambiguous substring. Some lpc commands are available to all users; oth- ers are available only to super-users. All users may execute the following lpc commands: ? [command ...] | help [command ...] Displays a short description of command. command is an lpc command. If command is not specified, displays a list of lpc commands. exit | quit Exits from lpc. status [all | printer ...] Displays the status of print daemons and print queues. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. Only a super-user may execute the following lpc commands: abort [all | printer ...] Terminates an active spooling daemon. Disables printing (by preventing new daemons from being started by lpr(1B)) for printer. all specifies this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. clean [all | printer ...] Removes files created in the print spool directory by the print daemon from printer 's print queue. all specifies that this command is performed on all locally attached printers.printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. disable [all | printer ...] Turns off the print queue for printer. Prevents new printer jobs from being entered into the print queue for printerby lpr(1B). all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. down [all | printer ...] [message] Turns the queue for printer off and disables printing on printer. Inserts message in the printer status file. message does not need to be quoted; multiple arguments to message are treated as arguments are to echo(1). Use down to take a printer down and inform users. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. enable [all | printer ...] Enables lpr(1B) to add new jobs in the spool queue. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. restart [all | printer ...] Attempts to start a new printer daemon. restart is useful when a print daemon dies unexpectedly and leaves jobs in the print queue. all specifies that this command is performed on all locally attached printers. printer indicates that this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. start [all | printer ...] Enables printing. Starts a spooling daemon for the printer. all specifies that this command is performed on all locally attached printers. printer indicates the command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. stop [all | printer ...] Stops a spooling daemon after the current job is complete. Disables printing at that time. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. topq printer [request-ID ...] [user ...] Moves request-ID or print jobs belonging to user on printer to the beginning of the print queue. Specify user as a user's login name. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. up [all | printer ...] Turns the queue for printer on and enables printing on printer. Deletes the message in the printer status file (inserted by down). Use up to undo the effects of down. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf( 4) for information regarding naming conventions for atomic names. EXIT STATUS
The following exit values are returned: 0 Successful completion. non-zero An error occurred. FILES
/var/spool/lp/* LP print queue. /var/spool/lp/system/pstatus Printer status information file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscplp | +-----------------------------+-----------------------------+ SEE ALSO
echo(1), lpq(1B), lpr(1B), lprm(1B), lpstat(1), lpsched(1M), lpshut(1M), svcadm(1M), printers.conf(4), attributes(5) DIAGNOSTICS
Use the svcs(1) utility to check if svc:/application/print/server is running. If it is not running, use svcadm enable svc:/applica- tion/print/server to start lpsched. See svcadm(1M). Ambiguous command Indicates that the lpc command or abbreviation matches more than one command. ?Invalid command Indicates that the lpc command or abbreviation is not recognized. ?Privileged command Indicates that the lpc command or abbreviation can be executed only by a super-user. lpc: printer: unknown printer to the print service Indicates that printer does not exist in the LP database. Check that printer was correctly specified. Use lpstat -p or the status command (see lpstat(1) or USAGE) to check the status of printers. lpc: error on opening queue to spooler Indicates that the connection to lpsched failed. Usually means that the printer server has died or is hung. Use /usr/lib/lp/lpsched to check if the printer spooler daemon is running. lpc: Can't send message to LP print service lpc: Can't receive message from LP print service Indicates that the LP print service stopped. Contact the LP administrator. lpc: Received unexpected message from LP print service Indicates a problem with the software. Contact the LP administrator. SunOS 5.10 5 Aug 2004 lpc(1B)

Featured Tech Videos