man synopsis standard compliance Post: 302149343

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Hello, I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password. This scares me, for a bunch of reasons. Mainly, one is that we...

2. Shell Programming and Scripting

standard error to standard out question

Hi there how can i get the result of a command to not give me its error. For example, on certain systems the 'zfs' command below is not available, but this is fine becaues I am testing against $? so i dont want to see the message " command not found" Ive tried outputting to /dev/null 2>&1 to no...

3. UNIX for Dummies Questions & Answers

Redirect Standard output and standard error into spreadsheet

Hey, I'm completely new at this and I was wondering if there is a way that I would be able to redirect the log files in a directories standard output and standard error into and excel spreadsheet in anyway? Please remember don't use too advanced of terminology as I just started using shell...

4. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:...

5. OS X (Apple)

POSIX compliance...

Thanks to all you guys about posix compliance I have learnt an enormous amount over the last few days. I have written a program that is an Egg Timer with simple animation. I now realise how sophisticated 'bash' is compared to full posix compliance. The code below has passed all of the tests from...

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)