Restarting the Spooler


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Restarting the Spooler
# 1  
Old 09-29-2006
Question Restarting the Spooler

Smilie Everytime our UNIXWARE 7 Server is restarted we also have to restart the spooler. If the spooler is not restarted, print jobs get stuck in the queu. Once restarted by using the following command lpstop and lpstart everything works fine.

Does anyone have any ideas what could be causing this or what can be done to fix it; without having to restart the spooler each time we restart the server?

Looking forward to your help

Thanks
 
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. SCO

SCO: UNIX Spooler

I have a system that will not allow me to print from any network printers. The printers are setup correctly. I have already used lpshut and lpsched to reset the spooler I am able to print jobs as long as I go around the spooler. However, anytime I attempt to send a job through spooler it... (9 Replies)
Discussion started by: T Long
9 Replies

2. UNIX for Dummies Questions & Answers

Print spooler

:eek: I need to check the status of my print spooler on an HP-UX what is the command? Thanks Janelle (1 Reply)
Discussion started by: lilnixon
1 Replies

3. UNIX for Dummies Questions & Answers

Question about spooler

I use software in Unix, I am trying to edit the file before final printing. Because the software only let me enter the data into, then print out, during printing, unix will save file buffer in some where to be ready print, if now I cancel the printing job, the file's buffer should be in spool, and... (3 Replies)
Discussion started by: wendyz
3 Replies

4. Shell Programming and Scripting

Print Spooler Script

I have posted before about this; but I am not sure I was clear on my message, so I am hoping someone can help with this as I gathered more information. Excuse me if I am not making sense...I am new to UNIXWARE :-( The print spooler start script was adjusted according to another engineer... (4 Replies)
Discussion started by: Yorgy
4 Replies

5. HP-UX

Unix Spooler - Hp deskjet

W eare currently running a Unix printer spooler and HP Deskjet printers. We are trying to set up a printer on the spooler server, but are getting connection errors. While we are able to ping and telnet to the relevant HP printer, we cannot set them up. Response: - The HP JetDirect Printer... (0 Replies)
Discussion started by: Vegas
0 Replies

6. HP-UX

Spooler Problem

Greetings, I have encountered the following errors and printing stops frequently. " ERROR 45 FROM LOCKF CALL ON FILE OUTPUTQ". I restart the spooler repeatedly but that is not a permanent solution. Please give me your usual assistance. With regards, Wobitu (2 Replies)
Discussion started by: wobitu
2 Replies
Login or Register to Ask a Question
RESTART_SYSCALL(2)					     Linux Programmer's Manual						RESTART_SYSCALL(2)

NAME
restart_syscall - restart a system call after interruption by a stop signal SYNOPSIS
int restart_syscall(void); Note: There is no glibc wrapper for this system call; see NOTES. DESCRIPTION
The restart_syscall() system call is used to restart certain system calls after a process that was stopped by a signal (e.g., SIGSTOP or SIGTSTP) is later resumed after receiving a SIGCONT signal. This system call is designed only for internal use by the kernel. restart_syscall() is used for restarting only those system calls that, when restarted, should adjust their time-related parameters--namely poll(2) (since Linux 2.6.24), nanosleep(2) (since Linux 2.6), clock_nanosleep(2) (since Linux 2.6), and futex(2), when employed with the FUTEX_WAIT (since Linux 2.6.22) and FUTEX_WAIT_BITSET (since Linux 2.6.31) operations. restart_syscall() restarts the interrupted system call with a time argument that is suitably adjusted to account for the time that has already elapsed (including the time where the process was stopped by a signal). Without the restart_syscall() mechanism, restarting these system calls would not correctly deduct the already elapsed time when the process continued execution. RETURN VALUE
The return value of restart_syscall() is the return value of whatever system call is being restarted. ERRORS
errno is set as per the errors for whatever system call is being restarted by restart_syscall(). VERSIONS
The restart_syscall() system call is present since Linux 2.6. CONFORMING TO
This system call is Linux-specific. NOTES
There is no glibc wrapper for this system call, because it is intended for use only by the kernel and should never be called by applica- tions. The kernel uses restart_syscall() to ensure that when a system call is restarted after a process has been stopped by a signal and then resumed by SIGCONT, then the time that the process spent in the stopped state is counted against the timeout interval specified in the original system call. In the case of system calls that take a timeout argument and automatically restart after a stop signal plus SIGCONT, but which do not have the restart_syscall(2) mechanism built in, then, after the process resumes execution, the time that the process spent in the stop state is not counted against the timeout value. Notable examples of system calls that suffer this problem are ppoll(2), select(2), and pselect(2). From user space, the operation of restart_syscall() is largely invisible: to the process that made the system call that is restarted, it appears as though that system call executed and returned in the usual fashion. SEE ALSO
sigaction(2), sigreturn(2), signal(7) Linux 2014-12-31 RESTART_SYSCALL(2)