07-01-2008
can't tell you exactly where the problem ist, but 5300-08-02-0822
was very buggy in our case
there where several problems with portmapper and rpcinfo, as non root user
our applications where not running after the upgrade (p570 Power6, hacmp5.4 SP2)
I removed ml08 , and everything was fine
i'll never apply an ml/fp one month after it was released again
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone know how to set the variables with the ipcs command?
I need to set the following variables:
Shared memory segments
message queues
semaphore arrays
all of these (1 Reply)
Discussion started by: Deuce
1 Replies
2. Programming
I am using SUN 0S 5.7.
My application has a dozen programs running in this machine, each instance of a program having 2 POSIX message queues for itself. Totally around 90 POSIX message queues.
Another small application uses a SYSTEM V shared memory and a message queue.
We face a problem... (1 Reply)
Discussion started by: Deepa
1 Replies
3. Solaris
hi,
I need help with ipcs command on Solaris. What does it do and what are options b,m,o,q does. Here is the sample output of ipcs -oq and ipcs -bm
IPC status from <running system> as of Sun Sep 7 23:07:59 GMT 2008
T ID KEY MODE OWNER GROUP CBYTES QNUM... (4 Replies)
Discussion started by: krabu
4 Replies
4. UNIX for Dummies Questions & Answers
Hi folks,
Please advise which command/command line shall I run;
1) to display the command and its output on console
2) simultaneous to save the command and its output on a file
I tried tee command as follows;
$ ps aux | grep mysql | tee /path/to/output.txt
It displayed the... (7 Replies)
Discussion started by: satimis
7 Replies
5. AIX
I am trying to run myApplication which allocates Some amount of shared memory at startup.
It failed because not available shared memory are available.
But when i ran,
ipcs -m
it is displaying empty(i.e no shared memory allocated in system.)
Why "ipcs -m" is displaying empty ?
... (5 Replies)
Discussion started by: ashokd001
5 Replies
6. UNIX for Advanced & Expert Users
Hi,
I read the ipcs man page and am still very confused.
Basically, I just want to know whether the output from the ipcs command below means these are the current "TOTAL" memory usage in bytes on the server? Is this correct?
Thanks in advance.
ipcs command output below:
# ipcs... (2 Replies)
Discussion started by: newbie_01
2 Replies
7. Solaris
How to clear IPCS queue count in server? (2 Replies)
Discussion started by: Arasu123
2 Replies
8. Solaris
Hello All,
We have a working script which identifies and kills ipcs resources which havent been correctly killed during normal shutdowns.
It is working fine and dandy however there are some issues now.
Environment:
SunOS 5.10 Generic_148888-03 sun4u sparc SUNW,SPARC-Enterprise
... (4 Replies)
Discussion started by: icalderus
4 Replies
9. UNIX for Advanced & Expert Users
The ipcs -q command output includes a MODE column which tells user if the process is waiting on read or write on the queue. I used this in scripts on many systems (Solaris, AIX, SCO)
a snippet from man
MODE (all)
The facility access modes and flags: The mode consists of
11... (2 Replies)
Discussion started by: migurus
2 Replies
10. Shell Programming and Scripting
I am using UNIX to create a script on our system. I have setup my commands to append their output to an outage file. However, some of the commands return no output and so I would like something to take their place.
What I need
The following command is placed at the prompt:
TICLI... (4 Replies)
Discussion started by: jbrass
4 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)