09-07-2012
Please stop posting everything in the "Emergency" forum, just because you can. I can't believe that every thread you've created in the last nine months has been for an emergency.
Closed.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello people,
I'm attempting to setup a printer connection to a printer running off the NT printer server, but with little success.
I'm using the admintool, go to ADD printers...where it offers 'local' and 'access to printer'. I have chosen the 'access to printer' option as i'm attempting to... (1 Reply)
Discussion started by: colesy
1 Replies
2. UNIX for Dummies Questions & Answers
Hello.
I am trying to make work HP printer Deskjet 692C. I have
Solaris 9 x86.
I tried to use admintool:
I choosed 'HP-printer' and 'Postscript filter' options.
When I want to print something, instead of the text, the printer prints many pages of some kind of code or whatever...
... (1 Reply)
Discussion started by: Peter123456789
1 Replies
3. UNIX for Advanced & Expert Users
I have a printer installed over ADSL to a router at a remote location. A Windows printer queue has been setup and working and I can ping the IP address from the Solaris server.
I now want to add a printer queue for this printer under Solaris, but I am unsure how to setup a remote printer queue.... (0 Replies)
Discussion started by: miredale
0 Replies
4. UNIX for Dummies Questions & Answers
We have several Printers that are pointing to a print server that is now defunct. I need to point these printers to the new print server.
I am aware I need to change the configuration in /usr/spool/lp/admins/lp/printers/printername/configuration as well as in /etc/printers.conf.
However my... (0 Replies)
Discussion started by: tugger
0 Replies
5. AIX
Hi folks need some help here. We have a RS6000 running AIX. It is almost never used anymore, but we need to print off some data. I have a paralell printer conected to the parrallel port, but have no idea where to go from here. The printer was originall named named LP01. If the users telnetinto the... (2 Replies)
Discussion started by: prator
2 Replies
6. AIX
Hi All,
This is katherine and I am kind of new to AIX and has got the following request to set up the printer. Can anybody guide me to fullfill the following request step by step.
The request is as follows:
"We have been asked to set up the following printer in Oracle: UNIX queue
... (1 Reply)
Discussion started by: katherine2008
1 Replies
7. HP-UX
Hi Guys,
I have been trying to resolve a printing problem but nothing works out .
I have an Epson LQ 680 (dot matrix printer) . I need to print a file . The paper length should be 34 .Left margin should be 5. I have tried the following things after researching from the man pages.
pr -t... (24 Replies)
Discussion started by: Kar1234
24 Replies
8. UNIX for Advanced & Expert Users
I have Solaris-10 server and want to change default printer setting to Simplex (Instead of duplex, which is set currently). I am not able to see anything in conf file related to this setting.
Please help (2 Replies)
Discussion started by: solaris_1977
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have Aix 6.1.
Installed the Ricoh Unix print filter, to allow us to print to a Ricoh 5001.
So I send text documents to the printer using the qprt command and set the print job finishing options using the Ricoh commands passed using -o options.
Eg. qprt -Pfin200 -o collate=on -o text... (7 Replies)
Discussion started by: max5000
7 Replies
10. AIX
Hi All,
I have been trying to configure an HP laserjet printer on an AIX6.1 server through network as well as remote.
This is the first time i am configuring a printer on AIX.
I had been using smitty butwhile configuring, i am getting blank/stuck at "software to support the printer attachment... (10 Replies)
Discussion started by: Rockyc3400
10 Replies
LEARN ABOUT XFREE86
systemd.target
SYSTEMD.TARGET(5) systemd.target SYSTEMD.TARGET(5)
NAME
systemd.target - Target unit configuration
SYNOPSIS
target.target
DESCRIPTION
A unit configuration file whose name ends in ".target" encodes information about a target unit of systemd, which is used for grouping units
and as well-known synchronization points during start-up.
This unit type has no specific options. See systemd.unit(5) for the common options of all unit configuration files. The common
configuration items are configured in the generic [Unit] and [Install] sections. A separate [Target] section does not exist, since no
target-specific options may be configured.
Target units do not offer any additional functionality on top of the generic functionality provided by units. They exist merely to group
units via dependencies (useful as boot targets), and to establish standardized names for synchronization points used in dependencies
between units. Among other things, target units are a more flexible replacement for SysV runlevels in the classic SysV init system. (And
for compatibility reasons special target units such as runlevel3.target exist which are used by the SysV runlevel compatibility code in
systemd. See systemd.special(7) for details).
IMPLICIT DEPENDENCIES
There are no implicit dependencies for target units.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Target units will automatically complement all configured dependencies of type Wants= or Requires= with dependencies of type After=
unless DefaultDependencies=no is set in the specified units. Note that Wants= or Requires= must be defined in the target unit itself --
if you for example define Wants=some.target in some.service, the automatic ordering will not be added.
o Target units automatically gain Conflicts= dependency against shutdown.target.
EXAMPLE
Example 1. Simple standalone target
# emergency-net.target
[Unit]
Description=Emergency Mode with Networking
Requires=emergency.target systemd-networkd.service
After=emergency.target systemd-networkd.service
AllowIsolate=yes
When adding dependencies to other units, it's important to check if they set DefaultDependencies=. Service units, unless they set
DefaultDependencies=no, automatically get a dependency on sysinit.target. In this case, both emergency.target and systemd-networkd.service
have DefaultDependencies=no, so they are suitable for use in this target, and do not pull in sysinit.target.
You can now switch into this emergency mode by running systemctl isolate emergency-net.target or by passing the option
systemd.unit=emergency-net.target on the kernel command line.
Other units can have WantedBy=emergency-net.target in the [Install] section. After they are enabled using systemctl enable, they will be
started before emergency-net.target is started. It is also possible to add arbitrary units as dependencies of emergency.target without
modifying them by using systemctl add-wants.
SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.special(7), systemd.directives(7)
systemd 237 SYSTEMD.TARGET(5)