Tapatalk Upgraded Post: 302940428

6 More Discussions You Might Find Interesting

1. Solaris

Sol10 upgraded from 5.8 - shell issues?

I'm having issues after upgrading to Sol10 from 8. I have developers who have ksh scripts which execute profiles and such. I get errors from "/dev/null: cannon create" to "stty:no such device or address", to "bad string", etc. I have checked the link to /dev/null (its fine). I have a case open with...

2. Programming

Getting the random failure after upgraded the gcc version 3.1 to 3.4.6

I am getting the a random failure after upgrading the gcc version 3.1 to 3.4.6. My code where it is failing contains some STL and shared memory concepts.It is perfectly working on old version of gcc.I want to know what are possible causes that made this random error after upgrading gcc 3.4.6.

3. OS X (Apple)

upgraded to OSX 10.6.6 - cannot sudo

I've been using "sudo" inside Terminal. I just upgraded to 10.6.6 and now "sudo" gives me incorrect password errors. My user is an admin user, so i can install etc on GUI but unable to do anything in terminal. 1. I did a repair permissions and restarted but cannot sudo. 2. i had an...

4. What is on Your Mind?

The ISS has upgraded to Linux

Remember this thread from a few years ago? What a difference just a few years make! Those laptops I mentioned were running Windows. Then one of the Russians got an infected thumb drive. It infected his laptop and spread throughout the ISS. NASA ordered a switch to Linux to ensure that it...

5. Solaris

Upgraded BIOS - cannot see Solaris partition??

I have recently upgraded my Supermicro X10SAT motherboard. I have also a SSD with a Windows10 partition and a Solaris 11.3 partition. Upon boot I press F11 and choose which partition I want to boot into. But after the bios upgrade, I cannot see the Solaris partition when I press "F11" to choose...

6. What is on Your Mind?

Cut Over to New Data Center and Upgraded OS Done. :)

Three days ago we received an expected notice from our long time data center that they were going dark on Sept 12th. About one and a half hours ago, after three days of marathon work, I just cut over the unix.com to a new data center with a completely new OS and Ubuntu distribution.

LEARN ABOUT PLAN9

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)