12-18-2003
mm
I have a problem with a printer in the unix network, is printing garbled. I assume the problem is in unix.
I think it was good to start by cancelling all printing jobs from that printer, but I wasn't able to do so. I just know to cancel jobs in lp -d formats.
The format of the printer's name is:
/dev/ttys12
Could you give me some help? I appreciate any suggestions.
Last edited by HN19; 12-18-2003 at 04:54 PM..
10 More Discussions You Might Find Interesting
1. HP-UX
Is it possible to create the CDROM device file for a drive attached to the parallel port? I have a removable CDROM drive (gift - I'm trying not to return it, but may have to anyways) that attaches via parallel port. The only device that I can attach to that hardware address is /dev/c1t0d0_lp, a... (9 Replies)
Discussion started by: LivinFree
9 Replies
2. UNIX for Advanced & Expert Users
Hi guys ...
i need ur help with some printing problem in unix ...
first prob. :
i wanna print from my NCR unix to an Win NT , Ip based printing server ( HP JetDirect ) .
My issue , is it possible to print directly to an Ip address from unix ?
How do i make it work to get any results ?... (3 Replies)
Discussion started by: QuickSilver
3 Replies
3. UNIX for Dummies Questions & Answers
Hi
I am trying to determine the access to unix devices. I found the follow access description which I have been told is a symbolic link and is not the actual file. I was also told that all symbolic links will have rwxrwxrwx access.
kmem: lrwxrwxrwx 1 root 27 May 28 16:06 /dev/kmem ->... (2 Replies)
Discussion started by: GW01
2 Replies
4. UNIX for Dummies Questions & Answers
How can I display the devices attached to my computer through the command line? And, how do I get information about each device listed? I'm looking to make sure that my DLT drive is recognized by the computer.
Using FreeBSD, if that helps.
Thanks! (1 Reply)
Discussion started by: derekc132002
1 Replies
5. Solaris
Hi all,
what does this mean?
if
then
<something>
fi
here is what i know..
it checks if the specified argument no($devid) in some function call is made into a block device and then proceeds with the execution of the loop.
However am not understand what lofi@0:means?
also is there... (3 Replies)
Discussion started by: wrapster
3 Replies
6. UNIX for Dummies Questions & Answers
I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment.
As an example, we have a tape library and giving the command
"camcontrol devlist" gives the following output:
akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies
7. UNIX for Dummies Questions & Answers
Hi folks,
I am trying to learn Unix based in Linux...
In Linux, in /Dev are files related to cards, mouse, etc..
how about Unix?
What is the difference between /Dev and /Devices?
Thanks,
Fernanda (0 Replies)
Discussion started by: ffpradella
0 Replies
8. Programming
Hi guys.
what is the benefits of using raw devices in programming?
which applications mostly use raw devices?
how can i use raw devices in C programs? is there any system calls or library functions? (1 Reply)
Discussion started by: majid.merkava
1 Replies
9. Windows & DOS: Issues & Discussions
We are using Red Hat. We have a issue like this: We want to print from Linux, to a printer attached to a Windows machine. What we want to print is a PDF. It prints, but the printing starts from the middle of the page. In the report, there is no space at the top but still printing starts from the... (5 Replies)
Discussion started by: rohan69
5 Replies
10. UNIX for Dummies Questions & Answers
Hi,
We have a Unix 3.2v5.0.5.
I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts).
This is the configuration file :
Code:
root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies
init(8) System Manager's Manual init(8)
NAME
init - Process control initialization
SYNOPSIS
/sbin/init [0123456789MmQqSs]
DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in
the inittab file. The init program reads and processes the entries in the inittab file.
The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at
that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab
file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init
that tell it which run level to change to.
Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab
file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the
initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the
user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the
virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a
message on the console stating the location of the virtual console.
To change the run level, the user specifies either the 0, 2, 3, or s flag.
For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run
level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these
entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file
systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to
be handled for that level.
Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child
process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal
that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new
entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi-
ately reexamine the inittab file, invoke the init program with the q flag.
FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a
multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no
such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces
init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from
/etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter-
minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single
user state with only the essential kernel services.
FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file
RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8)
Calls: kill(2), reboot(2)
Files: inittab(4) delim off
init(8)