09-02-2007
Remove it from /etc/inetd.conf.
Then restart inetd i.e.
kill -HUP pid
where pid is the inetd daemon's process id.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am putting a shell script in cron of root for solaris 7 server . This shell script runs rsh
commands within the script. The result is the shell script does not run in cron. The cron syntax is perfect.
When I run stand alone manually it works fine.I undesrstand I need to initialize everything... (6 Replies)
Discussion started by: Hitesh Shah
6 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone, I'n new on this... And I don't have experience.
I need to know how to enable rsh between solaris and tru64.
I don't know what i need to modify or install. I really don't have idea.
If somebody has documentation about this, or has a procedure to do this.
I really will... (1 Reply)
Discussion started by: cm247a
1 Replies
3. Solaris
Hi Guys,
Please suggest how to stop rsh on Solaris 10
Thanks
Manu (1 Reply)
Discussion started by: b_manu78
1 Replies
4. UNIX for Dummies Questions & Answers
All,
I have two AIX 5.3 systems that needs to run rsh commands on a Solaris 8 system, and one is failing. One, xx402 is a dedicated machine, and the other, xx452 is a virtual one on (via VIO).
The xx402 has no problem with the rsh commands but I keep getting "Permission Denied" when the... (5 Replies)
Discussion started by: kjbaumann
5 Replies
5. Solaris
Can any one tell me how to stop DHCP service on Solaris 10 so that it should not start nextime when the system is rebooted. (2 Replies)
Discussion started by: shabu
2 Replies
6. Solaris
Hi All,
I need to stop sendmail from running on boot-up. How can I do this on Solaris 8 and 9 sparc?
Please help and that you in advance. (2 Replies)
Discussion started by: itik
2 Replies
7. Solaris
Unable to execute commands using rsh in Solaris 9 and 10.
When I execute this command " rsh -n 172.16.67.91 ls -l " I am getting this error message.
::ffff:172.16.67.91: Connection refused
Please guide me how to enable rsh.
Thanks & Regards
Durgaprasad (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
8. UNIX for Dummies Questions & Answers
Can anyone point me in the right direction..
I have a test system which requires vxWorks to be loaded via TCPIP
I am using a Sun ultra10 box with Sol 9.0 installed as the server
I have configured the server and am able to load the boot image without any problems. I assume it is using the... (0 Replies)
Discussion started by: shortsrkt
0 Replies
9. Solaris
Hello to everybody from Argentina.
I need to stop samba because i need to fsck a filesystem
How can i do this?
I presume that the version is higher than 3.0.
/usr/sfw/sbin/smbd -D This is the out of ps -ef | grep smbd.
Thank you very much for your time i am a litle lost.
The... (4 Replies)
Discussion started by: enkei17
4 Replies
10. Solaris
Hi
we run rsh (password-less) among solaris 9/10 boxes very frequently and would like to know if there exist any logs which will capture either login session or the commands run (using rsh) or with any other info.
TIA
Reddy (0 Replies)
Discussion started by: reddyr
0 Replies
LEARN ABOUT DEBIAN
micro_proxy
micro_proxy(8) System Manager's Manual micro_proxy(8)
NAME
micro_proxy - really small HTTP/HTTPS proxy
SYNOPSIS
micro_proxy
DESCRIPTION
micro_proxy is a very small HTTP/HTTPS proxy. It runs from inetd, which means its performance is poor. But for low-traffic sites, it's
quite adequate. It implements all the basic features of an HTTP/HTTPS proxy, in only 260 lines of code.
To install it, add a line like this to /etc/inetd.conf:
webproxy stream tcp nowait nobody /usr/sbin/micro_proxy micro_proxy
Make sure the path to the executable is correct. Then add a line like this to /etc/services:
webproxy port/tcp
Change "port" to the port number you want to use - 3128, or whatever. Then restart inetd by sending it a "HUP" signal, or rebooting.
On some systems, inetd has a maximum spawn rate - if you try to run inetd services faster than a certain number of times per minute, it
assumed there's either a bug of an attack going on and it shuts down for a few minutes. If you run into this problem - look for syslog
messages about too-rapid looping - you'll need to find out how to increase the limit. Unfortunately this varies from OS to OS. On Free-
BSD, you add a "-R 10000" flag to inetd's initial command line. On some Linux systems, you can set the limit on a per-service basis in
inetd.conf, by changing "nowait" to "nowait.10000".
AUTHOR
Copyright (C) 1999 by Jef Poskanzer <jef@mail.acme.com>. All rights reserved.
16 March 1999 micro_proxy(8)