uhm... that's not good...
You (or your admin) should change that. Since Unix will check the directory permissions first, it may be possible for you to clobber a file... example:
( I almost put in something to do with /etc/passwd or /etc/shadow, but decided against it... don't want to contribute TOO much to delinquency...)
Like I said above, anything in /etc or /var can be overwritten... That's bad news.
I know i can look in the /etc/services file to look at referenced port numbers, but is there a command that will list the current ports being used? (i.e. what is the application does not have an entry in the services files :confused: ) (2 Replies)
Ok, I've been working in the IT field for about 3 years now and I never fully understood the concept of ip ports. I just started a new job that uses Solaris and today it kinda clicked in my head and I want to know if I'm right or wrong.
Does each ip address have multiple ports. because we... (4 Replies)
Hello UNIX people...
This is my first foray into the UNIX world so go easy on me...
I have a client who has hired me to do some work on his windows stuff, BUT it just so happens his UNIX server started giving him problems...
He is running SCO Open Server 5.0.6
The TTY ports won't... (5 Replies)
Hi ,
I need one help... Is there any command on solaris 10 to free the ports.
For e.g I used netstat -na| grep 8080
it displays either it is listening or established..
i want to free the ports...
Anyone please help me on this...
Thanks,
Shanmuga (2 Replies)
Hi,
If for example i try to start tomcat in a solaris server and get errors related to address already in use, how can I know if this port is really used for another process?
If someone can point any documentation it will be very helpfull.
Thanks! :rolleyes: (9 Replies)
When the netstat -an command is run on current unix machine, it seems that there's an excessive amount of ports established (roughly 600). How can I tell what each of these ports are being used for? (1 Reply)
** forum admins: Before you come down on my like a wrath of something, I can get no decent answers so I have to come to these Gurus' court ***
I am by no means Unix expert. However, none of our unix admin (aix & hpux) can give me an answer that makes sense.
My Issue:
Assigned ports in 8601,... (7 Replies)
Discussion started by: rsheikh
7 Replies
LEARN ABOUT NETBSD
mailer.conf
MAILER.CONF(5) BSD File Formats Manual MAILER.CONF(5)NAME
mailer.conf -- configuration file for mailwrapper(8)DESCRIPTION
The file /etc/mailer.conf contains a series of lines of the form
name program [arguments ...]
The first word of each line is the name of a program invoking mailwrapper(8). (For example, on a typical system /usr/sbin/sendmail would be
a symbolic link to mailwrapper(8), as would newaliases(1) and mailq(1). Thus, name might be ``sendmail'' or ``newaliases'' etc.)
The second word of each line is the name of the program to actually execute when the first name is invoked.
The further arguments, if any, are passed to the program, followed by the arguments mailwrapper(8) was called with.
The file may also contain comment lines, denoted by a '#' mark in the first column of any line.
The default mailer is postfix(1), which will also start by default (unless specifically disabled via an rc.conf(5) setting) so that locally
generated mail can be delivered, if the ``sendmail'' setting in /etc/mailer.conf is set to ``/usr/libexec/postfix/sendmail''.
FILES
/etc/mailer.conf
EXAMPLES
This example shows how to set up mailer.conf to invoke the postfix(1) program:
sendmail /usr/libexec/postfix/sendmail
mailq /usr/libexec/postfix/sendmail
newaliases /usr/libexec/postfix/sendmail
This example shows the use of the mini-sendmail package from pkgsrc in place of postfix(1):
# Send outgoing mail to a smart relay using mini-sendmail
sendmail /usr/pkg/sbin/mini-sendmail -srelayhost
send-mail /usr/pkg/sbin/mini-sendmail -srelayhost
Note the use of additional arguments.
SEE ALSO mail(1), mailq(1), newaliases(1), postfix(1), mailwrapper(8)
pkgsrc/mail/sendmail, pkgsrc/mail/mini_sendmail
HISTORY
mailer.conf appeared in NetBSD 1.4.
AUTHORS
Perry E. Metzger <perry@piermont.com>
BUGS
The entire reason this program exists is a crock. Instead, a command for how to submit mail should be standardized, and all the ``behave
differently if invoked with a different name'' behavior of things like mailq(1) should go away.
BSD April 10, 2010 BSD