01-20-2015
Yes, ................
?
So what's wrong? Do you get any errors from running the script?
8 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Can anyone suggest me from where to download the printer driver for HP 6L laserjet printer for servers/desktops having TRUE Unix-64 and Unixware 7.0 OS. (1 Reply)
Discussion started by: parbende
1 Replies
2. UNIX Desktop Questions & Answers
I am running a specialised program using a HP paintjet XL printer.
This printer is very old and ink cartriges are no longer available.
I want to use a HP 1102 C printer and need a driver.
Alternatively any A3 printer driver will do as long as the printer is still available.
Thanks
Louis (2 Replies)
Discussion started by: RAP
2 Replies
3. Linux
Hi, I just installed the Fedora Core 3, and now my printer cannot work because the Fedora Core 3 cannot find a suitable printer driver for it. It did recognize the model of my printer but just can't get the right printer driver. I am new to Linux, really hope someone can help me fix this problem,... (4 Replies)
Discussion started by: GarbageKing
4 Replies
4. Solaris
Hi,
I have a Solaris 9 box that is connected to an Intermec EasyCoder 3400e tag printer. We set up the printer in solaris 9 using Jet Direct Admin console to use dump blotter address and the whole thing works fine. We are now moving from the Solaris 9 box to Solaris 10 box and Jet Direct Admin... (2 Replies)
Discussion started by: mikies
2 Replies
5. Red Hat
Just got an HP OfficeJet L7680 printer but there are no drivers for it in RHEL5. I just want to add the single driver without installing hplip 3.9.8. It's going to be connected with USB. Is this possible and if so how? (1 Reply)
Discussion started by: deloev
1 Replies
6. UNIX for Dummies Questions & Answers
I have a RHEL 4 (probably not important, but whatever) machine with a few dozen network printers set up in CUPS. I would like to replicate this on a second machine.
With lpinfo I'm able to get the queue name and device information (socket://ipaddress or whatnot), but I haven't get figured out... (0 Replies)
Discussion started by: kknigga
0 Replies
7. UNIX for Dummies Questions & Answers
I need a virtual open source printer that can print to a text file. I need this printer to be open source because i will have to include it with my distribution of a program i am building.
Just for a little background information, i am going to be building a program to run inside of a... (5 Replies)
Discussion started by: bagstoper
5 Replies
8. Solaris
Hi Solaris 10 & possibly other Windows Gurus,
I am using hppi to setup IP based printers on Solaris 10 SPARC server but have always been having difficulty getting the exact driver for them. In this case it is for HP CP4525 series PCL6 so the only choice available was to choose the closest... (2 Replies)
Discussion started by: gjackson123
2 Replies
LEARN ABOUT FREEBSD
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)