08-20-2009
yes there is....see partial screenshot
lpsched(ADM) 4 December 1992 lpsched(ADM)
Name
lpsched, lpshut - start/stop the print service
Syntax
/usr/lib/lpsched [-d] [-f int] [-n int] [-r int] [-s]
/usr/lib/lpshut
Description
lpsched starts the LP print service; this can be done only by root or lp.
lpsched takes the following options:
-d Debug mode; this flag tells lpsched to log all messages between
lp and lpsched, all requests submitted, and all commands executed
by lpsched. The log files written to are messages, requests, and
exec in the /usr/spool/lp/logs directory.
:
also tried to run it on its full path...see below:
# pwd
/usr/lib
# ls -lt *lps*
---x--s--- 1 root lp 192646 Dec 29 1999 lpsched
---x--s--x 1 bin lp 26706 Mar 15 1993 lpshut
# lpshut
lpshut: not found
#
---------- Post updated at 10:34 AM ---------- Previous update was at 10:27 AM ----------
my bad......i think i now know where I went wrong......
looking at the full path......it's a script. ran it this way.
# cd /usr/lib
# ./lpshut
Print services stopped.
# ./lpsched
Print services started.
---------- Post updated at 10:45 AM ---------- Previous update was at 10:34 AM ----------
i have already did a lpshut & a lpsched.....still won't print to the HP laserjet?? am stuck...any more tips??
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I was just wondering if there is a way to recursive grep for something in this version of UNIX... so that I don't have to do it a directory at a time? (1 Reply)
Discussion started by: PBNOSGT
1 Replies
2. UNIX for Advanced & Expert Users
hi everybody
I have got a set of sco unix open server release 3.0 flopyy disks series N1, N2, M1, P1...P43, Release notes..
ý did a fresh installation. but ý cant install ethernet card. when ý use netconfig-ad a chain -tcpip... there is a messge :
the sco contain TCP/IP driver. and ý... (2 Replies)
Discussion started by: kaygusuz
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am a new user to the Server SCO OpenServer(TM) Release 5.
Could you please advise any books for me to have a comprehensive view of how to administrate this Unix server.
Thanks (1 Reply)
Discussion started by: rogercko
1 Replies
4. Filesystems, Disks and Memory
Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies
5. SCO
Hi Guys
I have got a problem and I would really be grateful if some1 could sort out the problem.
I have got a healthcare system named MEDISCAN, its SCO Unix based system, I need to convert the data files into ORACLE data.
The problem is that I have been unable to open the files, whatever... (1 Reply)
Discussion started by: Faysal_Mazhar
1 Replies
6. UNIX for Advanced & Expert Users
This question has been resolved. (0 Replies)
Discussion started by: system77
0 Replies
7. SCO
HI,
I have sco unix server currently i am trying to boot its not booting and giving error as HTFS error message contains -
Warning : can not identify block 496 for i number 438 on HTFS dev hd (1/42).
Warning : exit - /etc/init (PID 1) died, status 0x0000008B
server is not getting boot... (0 Replies)
Discussion started by: islamsk
0 Replies
8. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies
9. SCO
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies
10. UNIX for Advanced & Expert Users
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (5 Replies)
Discussion started by: Joaoalpande
5 Replies
LEARN ABOUT DEBIAN
socklog
socklog(8) System Manager's Manual socklog(8)
NAME
socklog - small and secure syslogd replacement for use with runit
SYNOPSIS
socklog [-rRU] [unix] [path]
socklog [-rR] inet [ip] [port]
socklog [-rR] ucspi [args]
DESCRIPTION
socklog is run under runit's runsv(8), writing syslog messages it receives from unix domain socket path or an inet udp socket ip:port
through a pipe provided by runsv(8) to a svlogd(8) process.
socklog can be run as an ucspi application to listen to an unix domain stream socket and for more flexible distributed logging.
If the environment variables $UID and/or $GID are present, socklog drops permissions to those ids after creating and binding the socket
(not in ucspi mode).
socklog converts syslog facility and priority information to names (facility.priority:) as found in /usr/include/syslog.h at compile time
if present.
On solaris socklog also accepts sun_stream as first argument. Please see the web page for details.
UNIX SOCKET
socklog [ unix ] [ path ]
Starting socklog with the 1st argument unix, socklog will listen to the unix domain socket path. If path is omitted, the default /dev/log
is used.
The 1st argument may be omitted, default is unix.
INET SOCKET
socklog inet [ ip ] [ port ]
Starting socklog with the 1st argument inet, socklog will listen to the inet udp socket ip:port.
If ip starts with 0, socklog will bind to all local interfaces.
If port is less or equal 1024, socklog must be run by root.
port may be omitted, default is 514. ip may be omitted, default is 0.
socklog prepends a.b.c.d: to each syslog message it receives, where a.b.c.d is the ip address of the connecting system.
UCSPI MODE
socklog ucspi [ args ]
Starting socklog with the 1st argument ucspi, socklog will run as an ucspi application. Normally socklog will only be started in ucspi mode
by an ucspi server tool, such as tcpsvd(8), tcpserver(1) or unixserver.
For each arg, socklog will prepend $arg: to each syslog message, if the environment variable $arg is present (maximum is 8).
OPTIONS
-r raw. Write the raw syslog messages (no conversion of facility and priority) to the pipe, additionally to the log messages with sys-
log facility and priority converted to names.
-R raw only. Same as -r above, but write the raw syslog messages only.
-U respect umask. Don't set umask to 0 before creating a unix domain socket, but respect the current setting of umask(2). This option
only takes effect in unix mode.
SEE ALSO
sv(8), runsvdir(8), runsv(8), svlogd(8), tryto(1), uncat(1), socklog-check(8), tcpsvd(8), nc(1)
http://smarden.org/socklog/
http://smarden.org/runit/
AUTHOR
Gerrit Pape <pape@smarden.org>
socklog(8)