10-22-2009
yes I did. ipaddress and routing details are same as before the upgrade. Since these servers are on VMware, I reverted back one of the server and its just working fine as it was before the upgrade. I think some thing wrong with upgrade. dont know what it is. Thanks.
10 More Discussions You Might Find Interesting
1. SuSE
I recently installed SLES 10 on an x86 64bit blade server. I then installed vsftpd from the suse cds through network services; however after configuring the vsftpd.conf file, the server fails to start:
# /etc/init.d/vsftpd start
Starting vsftpd startproc: exit status of parent of... (5 Replies)
Discussion started by: dave521
5 Replies
2. Linux
Dear All,
I have two intel xeon servers running with SLES 10 on a cluster environment (Veritas Cluster 4.1 - 2 Node Cluster - Active Passive). Both the systems are having hardware RAID 1 for OS disk. Both the systems are having DVD writer.
I would like to take the OS backup on DVD which can... (0 Replies)
Discussion started by: jumadhiya
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
I would like to programmatically find if given OS is SLES 10 / RHEL 3/.RHEL 4/RHEL5 etc ..
For this do we have any library call/sys call? Or should we use any sys. structure which would give me detailed info. Share me if you have any pointers.
Thanks in advance
- Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies
4. SuSE
Is there any doc/procedure to set up VNC on SLES 11 to connect from windows clients?? (1 Reply)
Discussion started by: s_linux
1 Replies
5. SuSE
Hi,
I am using
SUSE Linux Enterprise Server 11 (x86_64), PATCHLEVEL = 0 as NIS server.
All client is having SUSE Linux Enterprise Desktop 11 (x86_64), PATCHLEVEL = 0.
All system are configured to work in GUI.
When NIS user say 'a' locks system, and user 'b' wants to login to the same system... (1 Reply)
Discussion started by: sachingujrathi
1 Replies
6. SuSE
Hello,
I would like to change a password of a user to a simple one but when i try to add an only lowercase pass i get the error:
Weak password: too short.
Try again.
You can now choose the new password.
A valid password should be a mix of upper and lower case letters,
digits, and... (2 Replies)
Discussion started by: @dagio
2 Replies
7. SuSE
Can anyone give me a little clue on why the hard drive cache read timings on sles 9 is better then sles 11? The same hardware was used in both test. I even deleted the ata_generic module from initrd.
The speed difference is 10MB vs 5 MB
Thanks (1 Reply)
Discussion started by: 3junior
1 Replies
8. SuSE
I had sles 11 sp2 installed on my system some days back and it was running fine.
Today after I restarted my system the gui is not coming up and system starts in command terminal.
sax2 command returns error:
sax: gui is missing, starting command line interface
sax: no x-server... (4 Replies)
Discussion started by: rupeshkp728
4 Replies
9. SuSE
I had installed svn on SLES 11 using comands:
zypper addrepo http://download.opensuse.org/repositories/devel:tools:scm:svn/SLE_11/devel:tools:scm:svn.repo
zypper refresh
zypper install subversion
But when I run svn it gives me error as:
linux-uw85:~/Desktop # svn help
svn: error while... (4 Replies)
Discussion started by: rupeshkp728
4 Replies
10. SuSE
Hello All,
I'm trying to configure a SLES 10.3 machine as our Zypper server. I created the zypper directories with all the RPMs, made the directory structure accessible over HTTP but I'm stuck at the final stage: createrepo.
Looks like 'createrepo' is not present on this version :confused:
... (3 Replies)
Discussion started by: satish51392111
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)