Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Communicating Via Terminals With Other Computers Post 302236686 by vbe on Tuesday 16th of September 2008 05:11:27 AM
Old 09-16-2008
If it could not, unix would certainly not be such a success from the beginning...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Making X terminals out of a PC

Well I was trying to configure an Old PC having Win 3.1 to speak X with my UNIX server . I looked at notes , Looks like Debian Linux gives a base tarball to help boot of a floppy and talk to the XDMCP server . Well I was just hoping if there are other open source tools out there which would... (1 Reply)
Discussion started by: DPAI
1 Replies

2. UNIX for Dummies Questions & Answers

view all others terminals

i'm responsible for maintenance at my place and would like to watch all terminals in front me.i log myself into one terminal, but would like to view copy of other's terminals visible to me, it is just like for audit/security watch. (2 Replies)
Discussion started by: vkandati
2 Replies

3. UNIX for Advanced & Expert Users

How to use 2 Proccess communicating with each other using 2 pipe

Hi, Guys ... I want to know how to use to 2 processes (A & B) communicating with each others through 2 pipes (Pipe1 & Pinpe2) : such that process A write to Pipe1 and Process B read from Pipe1 and process B write to Pipe2 and Process A read from Pipe2 . Does anyone have an idea about... (1 Reply)
Discussion started by: someone33
1 Replies

4. UNIX for Advanced & Expert Users

Communicating with Serial Port

I am using system running on red hat linux 4. I had connected health measuring machine to the serial port and configured it stty -F /dev/ttyS0 9600 -parenb cs8 -cstopb this machine requires a command to be passed to it for giving output. I am unable to pass command hexa format(0x68) to the... (4 Replies)
Discussion started by: netsavant
4 Replies

5. AIX

how to know my serial port is communicating and running fine

i want to know that my serial port ( pci slot with 2 port ) is working fine and communicating is there any way to know the serialport is working and communicating? please help (3 Replies)
Discussion started by: pchangba
3 Replies

6. Programming

ERROR while communicating with gmail

$./a.out smtp.gmail.com 25 220 mx.google.com ESMTP 9sm2923369yxf.23 250 mx.google.com at your service 220 2.0.0 Ready to start TLS after handshake Common Name: smtp.gmail.com after get cert dn -----BEGIN SSL SESSION PARAMETERS-----... (0 Replies)
Discussion started by: darshan.ghumare
0 Replies

7. UNIX Desktop Questions & Answers

non-overlapping terminals

Hi Everyone! I was wondering if there's an easy way to have terminals (gnome-terminal for instance) be open in such a way that they're not overlapping each other? I suppose I could play around with the --geometry option but that would imply me checking whether a terminal is already at a given... (3 Replies)
Discussion started by: anthalamus
3 Replies

8. Programming

Child threads communicating with main thread via pipes

I have a simple client/server program I am using for learning purposes. I have it setup so that after server is setup and listening it than goes into a loop where it accepts incoming client connections. After each connection, the client socket is than passed to a thread routine where it can be... (3 Replies)
Discussion started by: Majortom71
3 Replies

9. Shell Programming and Scripting

Communicating with ethernet to serial LED sign - is this feasible?

I have a london-electronics LED sign I picked up on eBay which I would like to display custom messages on programmatically. It is working ok. Opening it up, it has an ethernet to serial connection currently plugged in and a serial connection currently unplugged internally (same connectors).... (9 Replies)
Discussion started by: windswept321
9 Replies
socklog(8)						      System Manager's Manual							socklog(8)

NAME
socklog - small and secure syslogd replacement for use with runit SYNOPSIS
socklog [-rRU] [unix] [path] socklog [-rR] inet [ip] [port] socklog [-rR] ucspi [args] DESCRIPTION
socklog is run under runit's runsv(8), writing syslog messages it receives from unix domain socket path or an inet udp socket ip:port through a pipe provided by runsv(8) to a svlogd(8) process. socklog can be run as an ucspi application to listen to an unix domain stream socket and for more flexible distributed logging. If the environment variables $UID and/or $GID are present, socklog drops permissions to those ids after creating and binding the socket (not in ucspi mode). socklog converts syslog facility and priority information to names (facility.priority:) as found in /usr/include/syslog.h at compile time if present. On solaris socklog also accepts sun_stream as first argument. Please see the web page for details. UNIX SOCKET
socklog [ unix ] [ path ] Starting socklog with the 1st argument unix, socklog will listen to the unix domain socket path. If path is omitted, the default /dev/log is used. The 1st argument may be omitted, default is unix. INET SOCKET
socklog inet [ ip ] [ port ] Starting socklog with the 1st argument inet, socklog will listen to the inet udp socket ip:port. If ip starts with 0, socklog will bind to all local interfaces. If port is less or equal 1024, socklog must be run by root. port may be omitted, default is 514. ip may be omitted, default is 0. socklog prepends a.b.c.d: to each syslog message it receives, where a.b.c.d is the ip address of the connecting system. UCSPI MODE
socklog ucspi [ args ] Starting socklog with the 1st argument ucspi, socklog will run as an ucspi application. Normally socklog will only be started in ucspi mode by an ucspi server tool, such as tcpsvd(8), tcpserver(1) or unixserver. For each arg, socklog will prepend $arg: to each syslog message, if the environment variable $arg is present (maximum is 8). OPTIONS
-r raw. Write the raw syslog messages (no conversion of facility and priority) to the pipe, additionally to the log messages with sys- log facility and priority converted to names. -R raw only. Same as -r above, but write the raw syslog messages only. -U respect umask. Don't set umask to 0 before creating a unix domain socket, but respect the current setting of umask(2). This option only takes effect in unix mode. SEE ALSO
sv(8), runsvdir(8), runsv(8), svlogd(8), tryto(1), uncat(1), socklog-check(8), tcpsvd(8), nc(1) http://smarden.org/socklog/ http://smarden.org/runit/ AUTHOR
Gerrit Pape <pape@smarden.org> socklog(8)
All times are GMT -4. The time now is 01:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy