04-03-2014
Quote:
Server. Does it make a difference
Well I saw many station with init default=2...
Problem from Solaris10 and above, rc stuff is considered as legacy...
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Expert,
I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0..
I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies
2. SCO
I have 2 questions :
----------------------------------
1 - How can I execute a program when Unix Sco reboot?
For example I have two script (two sockets) that I have to
start from 2 different users (root and toto).
I heard something about "etc/init.d" directory, but I don't know what to... (4 Replies)
Discussion started by: soshell
4 Replies
3. Linux
Dear all,
I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel):
1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins
So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies
4. Shell Programming and Scripting
Create a script that copies files from one specified directory to another specified directory, in the order they were created in the original directory between specified times. Copy the files at a specified interval. (2 Replies)
Discussion started by: allways4u21
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS.
When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies
6. Red Hat
I encountered a problem on one of our database servers.
OS: CentOS 5.5 final
Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel)
We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies
7. Red Hat
Hi ppl hope to have your advice, i am run out of idea...
I have 3 scripts: a.sh, b.sh, and c.sh
a.sh resided in /etc/init.d
b.sh and c.sh /opt/xSystem
I intend to start my system with "service" command which will trigger my a.sh
service a.sh start
then.
a.sh will trigger... (4 Replies)
Discussion started by: cielle
4 Replies
8. Shell Programming and Scripting
Hello All,
I copied and pasted the "/etc/init.d/skeleton" file to a new one so I could create my own init script for a program.
Basically the ONLY edit I made to the skeleton "template" so far was to search and replace "FOO" with "snort".
*NOTE: I know there are a bunch of snort init scripts... (6 Replies)
Discussion started by: mrm5102
6 Replies
9. Shell Programming and Scripting
Hi All,
I'm trying to build a start up script, wud be gr8 if any one can explain what the below field means and how can i check it for my script.
DAEMON_PATH="/home/wes/Development/projects/myapp"
DAEMON=myapp
DAEMONOPTS="-my opts"
NAME=myapp
DESC="My daemon description"... (4 Replies)
Discussion started by: Karthick N
4 Replies
10. Linux
This is what I did:
1. I wrote a simple init.d script (myscript.sh)
2. I placed it under /etc/init.d (where many other default scripts already are)
3. Set the perms to 755
4. Run: update-rc.d myscript.sh defaults
I can run it perfectly by doing:
/etc/init.d/myscript.sh start... (2 Replies)
Discussion started by: rlopes
2 Replies
LEARN ABOUT MOJAVE
net::server::proto::unix5.18
Net::Server::Proto::UNIX(3) User Contributed Perl Documentation Net::Server::Proto::UNIX(3)
NAME
Net::Server::Proto::UNIX - Net::Server UNIX protocol.
SYNOPSIS
See Net::Server::Proto.
DESCRIPTION
Protocol module for Net::Server. This module implements the UNIX SOCK_STREAM socket type. See Net::Server::Proto.
Any sockets created during startup will be chown'ed to the user and group specified in the starup arguments.
PARAMETERS
The following paramaters may be specified in addition to normal command line parameters for a Net::Server. See Net::Server for more
information on reading arguments.
unix_type
Can be either SOCK_STREAM or SOCK_DGRAM (default is SOCK_STREAM). This can also be passed on the port line (see Net::Server::Proto).
However, this method is deprecated. If you want SOCK_STREAM - just use proto UNIX without any other arguments. If you'd like
SOCK_DGRAM, use the new proto UNIXDGRAM.
METHODS
NS_unix_path/NS_unix_type
In addition to the standard NS_ methods of Net::Server::Proto classes, the UNIX types also have legacy calls to NS_unix_path and
NS_unix_type.
Since version 2.000, NS_unix_path is simply an alias to NS_port. NS_unix_type is now redundant with NS_proto.
These methods were missing between version 2.000 and 2.003 but have been returned as legacy bridges.
QUICK PARAMETER LIST
Key Value Default
# deprecated UNIX socket parameters
unix_type (SOCK_STREAM|SOCK_DGRAM) SOCK_STREAM
port "filename" undef
# more recent usage
port "filename / UNIX"
port "filename / UNIXDGRAM"
LICENCE
Distributed under the same terms as Net::Server
perl v5.18.2 2012-06-06 Net::Server::Proto::UNIX(3)