10 More Discussions You Might Find Interesting
1. Linux
I have someone wanting to connect to the serial management port of a switch from a PC running CentOS6. The management port on the switch is apparently baud 9600, 8 data bits, 1 stop bit & no parity They have plugged in a cable to connect and the output from lsusb is:-Bus 001 Device 001: ID... (7 Replies)
Discussion started by: rbatte1
7 Replies
2. AIX
HI,
Does anyone installed a GPS from his Serial port to an IBM Server serial port with AIX 5.X
I would like the rs232 configuration you used on the GPS, and the ttys configuration from your server.
Thanks in advance !!! (8 Replies)
Discussion started by: trevian3969
8 Replies
3. Red Hat
Hi all,
I am not able to telnet from one system to another.
say from system1 to system2
However i am able to do
telnet system2 1521
but I am not able to do
telnet system2 6730 &
telnet system2 6731 &
telnet system2 6732
some other onformation:
system1:root(/root)# rpm -qa |... (1 Reply)
Discussion started by: manalisharmabe
1 Replies
4. UNIX Desktop Questions & Answers
Hi Guys,
my issue is - I have people connecting to my hosts from the outside world (for POC testing). There application listens on a port 3010 which is bound to the localhost. Using netstat -an | grep LISTEN it is the only port that is bound - ie: ftp, ssh etc listen on all interfaces. I need... (1 Reply)
Discussion started by: brian112
1 Replies
5. AIX
Hello,
I have an old Pseries P520 9111-520 and it doesn't have the PCI graphics - video - display card in it.
On the back side of it, I can see two serial ports.
What is the easiest way to put console display for this system ?
Would a serial cable ( null modem cable ) from Pseries to... (5 Replies)
Discussion started by: filosophizer
5 Replies
6. Solaris
Hi
Gud day,
Im facing this problem on how to connect to solaris 8 service rlogind listening to port 513 using ssh. I had no luck in establishing a connection using ssh in the rlogind. is there a way that i something missed or dont know know on how to accomplished my objective. or theres no... (2 Replies)
Discussion started by: jao_madn
2 Replies
7. AIX
Hello AIX Group Members,
I have two systems: (1) IBM pSeries 640, 7026-B80. (2) A 5-month old HP laptop with Windows Vista. It has no serial port and only has USB ports on it.
My question are: How can I use the laptop as the p640's terminal? How can I make the connection? What type of cable... (4 Replies)
Discussion started by: aixlover
4 Replies
8. OS X (Apple)
Hi
Do I have to open my ssh port if I like to connect to another machine?
- if yes, how?
Or is that only if I want to access my one computer from the outside?
I run Mac OS 10.4 and like to access a unix box on the other side.
/andreas (1 Reply)
Discussion started by: lulle
1 Replies
9. UNIX for Advanced & Expert Users
Hi is there any way to connect through com port to using shell script.
Thanks in advance. (1 Reply)
Discussion started by: yhacks
1 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I have been using a computer to keep track of inventory for my business. I am pretty sure it runs on Unix. In the back of the computer there is some sort of PCI card that has about 8 RJ-11 ports on it. I use that card to connect the Unix system to my 3 VT-220 terminals. I use a simple 6... (1 Reply)
Discussion started by: john202
1 Replies
svnserve(8) System Manager's Manual svnserve(8)
NAME
svnserve - Server for the 'svn' repository access method
SYNOPSIS
svnserve [options]
DESCRIPTION
svnserve allows access to Subversion repositories using the svn network protocol. It can both run as a standalone server process, or it
can run out of inetd. You must choose a mode of operation when you start svnserve. The following options are recognized:
-d, --daemon
Causes svnserve to run in daemon mode. svnserve backgrounds itself and accepts and serves TCP/IP connections on the svn port (3690,
by default).
--listen-port=port
Causes svnserve to listen on port when run in daemon mode.
--listen-host=host
Causes svnserve to listen on the interface specified by host, which may be either a hostname or an IP address.
--foreground
When used together with -d, this option causes svnserve to stay in the foreground. This option is mainly useful for debugging.
-i, --inetd
Causes svnserve to use the stdin/stdout file descriptors, as is appropriate for a daemon running out of inetd.
-h, --help
Displays a usage summary and exits.
--version
Print svnserve's version and the repository filesystem back-end(s) a particular svnserve supports.
-r root, --root=root
Sets the virtual root for repositories served by svnserve. The pathname in URLs provided by the client will be interpreted relative
to this root, and will not be allowed to escape this root.
-R --read-only
Force all write operations through this svnserve instance to be forbidden, overriding all other access policy configuration. Do not
use this option to set general repository access policy - that is what the conf/svnserve.conf repository configuration file is for.
This option should be used only to restrict access via a certain method of invoking svnserve - for example, to allow write access via
SSH, but not via a svnserve daemon, or to create a restricted SSH key which is only capable of read access.
-t, --tunnel
Causes svnserve to run in tunnel mode, which is just like the inetd mode of operation (serve one connection over stdin/stdout) except
that the connection is considered to be pre-authenticated with the username of the current uid. This flag is selected by the client
when running over a tunnel agent.
--tunnel-user=username
When combined with --tunnel, overrides the pre-authenticated username with the supplied username. This is useful in combination with
the ssh authorized_key file's "command" directive to allow a single system account to be used by multiple committers, each having a
distinct ssh identity.
-T, --threads
When running in daemon mode, causes svnserve to spawn a thread instead of a process for each connection. The svnserve process still
backgrounds itself at startup time.
--config-file=filename
When specified, svnserve reads filename once at program startup and caches the svnserve configuration and any passwords and authoriza-
tion configuration referenced from filename. svnserve will not read any per-repository conf/svnserve.conf files when this option is
used. See the svnserve.conf(5) man page for details of the file format for this option.
--pid-file=filename
When specified, svnserve will write its process ID to filename.
-X, --listen-once
Causes svnserve to accept one connection on the svn port, serve it, and exit. This option is mainly useful for debugging.
Unless the --config-file option was specified on the command line, once the client has selected a repository by transmitting its URL,
svnserve reads a file named conf/svnserve.conf in the repository directory to determine repository-specific settings such as what authenti-
cation database to use and what authorization policies to apply. See the svnserve.conf(5) man page for details of that file format.
SEE ALSO
svnserve.conf(5)
svnserve(8)