8 More Discussions You Might Find Interesting
1. Web Development
I need your help please, Im a newbie at web applications and i am taking a course and i was struggling the web server to get to work
this is when the webeserver is up:
ubuntu@ubuntu-N53SV:~/hello_WWW$ rails server
=> Booting Puma
=> Rails 6.0.0 application starting in development ... (3 Replies)
Discussion started by: alexcol
In SOlaris 9 for eg, inside the /etc/init.d/inetsvc file,
you can set the tcp tracing by going to the last line and adding the following as :-
inetd -s -t &
In Solaris 10, I know we can use the svccfg to do it or with the inetadm command.
When I use inetadm -m command to set the tcp tracing... (3 Replies)
Discussion started by: incredible
I have been told to migrate linux init scripts to solaris 10. i am reading about the chkconfig & SMF ( I came to know that SMF is used in Sol 10 for service management ). The only thing i could not find out ( Because i dont have root access ) is how the links are created in rcX.d directory? ... (6 Replies)
Discussion started by: zedex
I would like to run command whenever system boot up, i.e "/opt/admin/script/closegen -c /opt/share/script/colsehg"
How do I integrate above command in to SMF services.
-sam (1 Reply)
Discussion started by: sam786
I have a Solaris server which runs version 10
After installing the patch , i thought of doing a recongiuration reboot
But it failed saying "smf repository not running"
what could be the issue.
J (4 Replies)
Discussion started by: jegaraman
6. Shell Programming and Scripting
I need the a help can please any one give me a suggestion for Exporting the CLASS PATH in service manifest file for Solaris 10
Here i have pasted the code
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<!-- Copyright 2007 Sun... (4 Replies)
Discussion started by: Shreedhar Naik
I have a default, sun supplied, apache2 install on solaris10. It's running fine, everything's great. I'm looking to add another instance, fairly happy with how to do that apart from one thing - the SMF manifest.
Can i just edit the XML file sun supplied for the default apache2 and add in details... (2 Replies)
Discussion started by: craigp84
8. UNIX for Dummies Questions & Answers
We are trying to run the WU_FTPD demon in standalone mode (-S argument) via an SMF service. Prior to SMF, this was achieved by simply commenting out the FTP line within the inetd.conf file. However, within SMF, I believe we need to carry out the following activities:
i) Remove the FTP... (0 Replies)
Discussion started by: CowsUdders
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
dh_systemd_start - start/stop/restart systemd unit files
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
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.
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.
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.
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 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.
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)