10-03-2009
Shut down all of the oracle instances running, then restart them.
10 More Discussions You Might Find Interesting
1. Linux
Hello!
How do make the limits.conf parameters work for a normal user. Ive changed
both the hard and soft parameter for the specific user. It used to be 4096 and i changed it to 16384. But when i use the ulimit -n, all i got is permissen denied.
Witch i can understand. But my question is? how... (1 Reply)
Discussion started by: dozy
1 Replies
2. UNIX for Dummies Questions & Answers
I have line in this file that says:
username - maxlogins 1
and user can login 2 times instad of one.
does enybody know why? and how can I fix that? (2 Replies)
Discussion started by: shooroop
2 Replies
3. UNIX for Advanced & Expert Users
HI,
To restrict the number of files and number of processes used the user we use the following configuration in the file /etc/security/limits.conf.
oracle soft nofile 65572
oracle hard nofile 65572
oracle soft noproc 16384
oracle soft noproc 16384
My question is what do the 'soft' and... (1 Reply)
Discussion started by: praveen_b744
1 Replies
4. Solaris
Hi,
How can we set per user core file size, etc in solaris, i.e. I want solaris counterpart/equivalent of linux /etc/security/limits.conf.
TIA (0 Replies)
Discussion started by: slash_blog
0 Replies
5. Solaris
Hi all,
Well, I was trying to resolve a VAS issue by modifying my pam.conf on a solaris 8 V210 server. I made a back-up of the pam.conf file.
But when I try to connect now, no connection is available.
I can go on the console through a hyperterminal connection, but the login does not work on... (2 Replies)
Discussion started by: portgas
2 Replies
6. Red Hat
i want to set limits in /etc/security/limits.conf.My os is rhel 5.2.
It was giving continuous messages in in /var/log/secure like :
continuously.
I have changed values of priority and nice to "0" from unlimited and messages are not comming. But i want to know what is the ideal/maximum... (3 Replies)
Discussion started by: pankajd
3 Replies
7. Linux
Hi there,
I am trying to set a ulimit max in the /etc/security/limits.conf against a NIS netgroup (which contains a whole bunch of users) instead of a local user or group.
so I have a NIS netgroup called +@myusers , none of whose users are defined locally on the box. I want to ensure that... (2 Replies)
Discussion started by: rethink
2 Replies
8. UNIX for Advanced & Expert Users
Hi,
can any body give light for my issue please,,I cannot ssh and also telnet to my solaris machine. I tried root and all other users on this machine. When I connect a terminal to my solaris machine via the serial mgt. port, I get the following error messages:
open_pam_conf: /etc/pam.conf... (1 Reply)
Discussion started by: aagusman
1 Replies
9. Linux
I've been looking online trying to find the correct value nice and priority can take in the limits.conf file. ON the man page it says;
Does this mean priority can be any negative number and any positive?
Then
Does this mean any number between -20 and 19 also what does the definition of nice... (13 Replies)
Discussion started by: matthewfs
13 Replies
10. UNIX for Dummies Questions & Answers
OS version : RHEL 6.5
Below is an excerpt from /etc/security/limits.conf file for OS User named appusr in our server
appusr soft nproc 2047
appusr hard nproc 16384
What will happen if appusr has already spawned 2047 processes and wants to spawn 2048th process ?
I just want to know... (3 Replies)
Discussion started by: kraljic
3 Replies
LEARN ABOUT HPUX
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)