Sponsored Content
Operating Systems HP-UX how to start the x window system Post 45029 by norsk hedensk on Sunday 14th of December 2003 12:52:28 AM
Old 12-14-2003
is x installed on your system? you probably dont have x installed on your system.

what errors are you gettting when you try to start x?
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

An X Window System from scratch

I'm currently using Gnome as my desktop environment (DE) but it's going kind of slow. My friend gave me the advice to skip the DE and only use a Window Manager. I took his suggestion one step further and decided to try building an X window system from scrath instead. But what are the... (3 Replies)
Discussion started by: J.P
3 Replies

2. Windows & DOS: Issues & Discussions

window 2000 professional not pinging my window 98 system.

Hello, We someone help me resolve this problem. I have window 2000 professional, windows 98 and Unixware 7.0.1 on the network. I was able to establish connection with all. However, l was unable to ping window 98 from window 2000 professional. I was able to ping the window 2000 from the window... (10 Replies)
Discussion started by: kayode
10 Replies

3. AIX

Q: how to start a service when system start

As topic, assume we have a service called "blahservice" and we can start it by: startsrc -s blahservice what is the best practice to run such command when system start? - directly use mkitab to add it into /etc/inittab or - drop startup scripts in /etc/rc.d/rcX.d I know they... (4 Replies)
Discussion started by: acerlinux
4 Replies

4. UNIX for Dummies Questions & Answers

What would take the Place of X Window System if X was not installed?

If X was not installed, what would print data onto the display? Does it include applications form Gpl/Gnu or is it a daemon only? Thanks in advance!:wall: (2 Replies)
Discussion started by: theKbStockpiler
2 Replies

5. UNIX for Dummies Questions & Answers

X Window system - concept

Hi, I am lost in between of some concepts, googling too much made me like this! honestly... please correct my statements below and if they are correct just mention "correct" or also add extra info please: 1. "X Window System" provides basic access to GUI on unix/linux systems This... (3 Replies)
Discussion started by: messi777
3 Replies

6. IP Networking

TCP initial congestion window (slow-start)

I have noticed that the initial congestion window in my traces is 8920bytes~=6*1448. rfc3390 states the initial cwand should be max 4000 bytes(around 3*1448). At first i thought it might be because i'm running my server on mac os x, so apple might have modified the tcp stack. Therefore I tried... (2 Replies)
Discussion started by: ddayan
2 Replies

7. HP-UX

How to start X window?

hi, here is a HP workstation C9000 with HP-UX system in my office. couple days ago we shutdown the system. when trying to turn the it on, the system failed to start X window. my boss ask me fix it, but i am new of unix world. please be kindly to teach me how to get error message and fix... (19 Replies)
Discussion started by: ethandaddy
19 Replies

8. AIX

Is XVFB(X window system virtual frame buffer ) open source

I would like to know XVFB is open source or not. (0 Replies)
Discussion started by: prathap.g
0 Replies

9. UNIX for Beginners Questions & Answers

Which X Window system is installed on my server that would work with Xming?

I would like to use Xming to connect a server and managed to get it to work. I am now trying to get it to connect to a different server but i am not sure which X Window system is installed. I tried it through putty and i get the following error/warning: /usr/java/jdk1.7.0_67/bin> jvisualvm... (5 Replies)
Discussion started by: ziggy25
5 Replies

10. Programming

Configure: error: X Window system libraries and header files are required

I am trying to compile thunar 1.8.4. It is giving me this error. configure: error: X Window system libraries and header files are required Ubuntu Mate 18.04 (2 Replies)
Discussion started by: drew77
2 Replies
DH_INSTALLSYSTEMD(1)						     Debhelper						      DH_INSTALLSYSTEMD(1)

NAME
       dh_installsystemd - install systemd unit files

SYNOPSIS
       dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...]

DESCRIPTION
       dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files.

       In the simple case, it finds all unit files installed by a package (e.g.  bacula-fd.service) and enables them. It is not necessary that the
       machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from
       sysvinit to systemd and back.

       For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and
       dh_installsystemd --name=quotarpc quotarpc.service.

FILES
       debian/package.service, debian/package@.service
	   If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build
	   directory.

       debian/package.tmpfile
	   If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is
	   currently only used by systemd.)

       debian/package.target, debian/package@.target
	   If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build
	   directory.

       debian/package.socket, debian/package@.socket
	   If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build
	   directory.

       debian/package.mount
	   If this exists, it is installed into lib/systemd/system/package.mount in the package build directory.

       debian/package.path, debian/package@.path
	   If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build
	   directory.

       debian/package.timer, debian/package@.timer
	   If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build
	   directory.

OPTIONS
       --no-enable
	   Disable the service(s) on purge, but do not enable them on install.

	   Note that this option does not affect whether the services are started.  Please remember to also use --no-start if the service should
	   not be started.

       --name=name
	   Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used,
	   dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service.
	   Moreover, maintainer scripts are only generated for units that match the given name.

       --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).

	   Note that this option does not affect whether the services are enabled.  Please remember to also use --no-enable if the services should
	   not be enabled.

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.

SEE ALSO
       debhelper(7)

AUTHORS
       pkg-systemd-maintainers@lists.alioth.debian.org

11.1.6ubuntu2							    2018-05-10						      DH_INSTALLSYSTEMD(1)
All times are GMT -4. The time now is 04:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy