03-05-2012
yes i already tried it but nothing happens
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have 3 solaris servers. Two servers of differnet network and one gateway.
Server1 --> 192.168.0.1 --> Solaris 9
Server2 --> 10.27.40.2 --> Solaris 10
Server3 --> Iface1 --> 192.168.0.5 --> Solaris 10 --> Gateway
Iface2 --> 10.27.40.5
Now I am able to ssh... (36 Replies)
Discussion started by: neel.gurjar
36 Replies
2. AIX
Hi All,
May be a dumb question to old AIX hacks, if so apologize.
I have worked with /etc/inittab on SCO, but apparently with AIX you should use the 'mkitab' command to add entries instead of just vi'ing the file.
I just need a daemon process (script called 'dpr_daemon') to kick off once and... (19 Replies)
Discussion started by: jeffpas
19 Replies
3. UNIX for Advanced & Expert Users
I'm becoming a dying breed where I work. More and more sys admins are advocating automatically restarting failed services such as tomcat, jboss, etc. I've always been against doing this except with buggy apps that can't be fixed or avoided.
My main argument is that I feel it's a trick used by... (9 Replies)
Discussion started by: mglenney
9 Replies
4. UNIX for Advanced & Expert Users
Hi
currently my linux instance is running in runlevel 3 ( someone has set the default to 3)
i have to change it to runlevel 5 . my question
1) does the editing of /etc/inittab needs system restart to enter runlevel 5.
2) how can we avoid system restart because if some users are... (3 Replies)
Discussion started by: rakeshkumar
3 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have a couch Db server running. I have written a script which will check and kill the multiple instances of the same and then start again a new one.
Now when i start the db server manually, the UI of the DB is accessible via browser. But when i do the same using cronjob, the UI of... (0 Replies)
Discussion started by: sarath@123
0 Replies
6. Shell Programming and Scripting
Hi Guys,
I need bash script to restart the service.
1. Disable the service called SASM
svcadm disable sasm
2. if service went to maintenance mode then it shuld clear it with below command
svcadm clear sasm
3.or else it should restart the mysql service
/etc/init.d/mysql stop... (1 Reply)
Discussion started by: bapu1981
1 Replies
7. AIX
Hello,
I have a problem with an NFS file system. Both AIX servers are AIX6.1 and uses NFS version 3.
The problem is that at some point the client server cannot connect to the NFS anymore and when i do df -k it displays the message NFS server <server> not responding still trying.
i run the... (2 Replies)
Discussion started by: omonoiatis9
2 Replies
8. Red Hat
I had a doubt if any services need to be restarted if port no in /etc/services in an RHEL setup is changed. For eg, the port no of 443 for SSL may need to be changed.
I hope my query is clear whether any services need to be restarted if port no in /etc/services is changed.
Please revert with... (10 Replies)
Discussion started by: RHCE
10 Replies
9. Debian
Hello,
I would like to do follow steps.
Set a static IP-Adress on eth0 (For Testing)
Set DHCP on eth0
All steps should be done without a single reboot.
/etc/network/interfaces
iface eth0 inet static
address 192.0.2.7/24
gateway 192.0.2.254How do i perform... (3 Replies)
Discussion started by: int3g3r
3 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)