irs
—
Accept incoming OBEX and COMM connections on IrDA
irs |
[-aAceghijoptY ]
[-d device]
[-l log_file]
[-m max_speed]
[-n station_name]
[-O oport]
[-s iport]
[-v verbose_level]
[-y pty] |
The irs
command accepts incoming OBEX objects and COMM
connections on IrDA. It writes the OBEX objects to files or a socket, and
connects the COMM connections to stdin/stdout or a pty. It can also accept
OBEX objects from a socket and send them via IrDA.
The options are as follows:
-a
- Use driver for ACTiSYS IR-220L dongle.
-A
- Use driver for ACTiSYS IR-220L+ dongle.
-c
- Act as COMM server, accepting COMM connections and connecting them to
stdin or a pty.
-d
- Specify IrDA device to use.
-e
- Exit on disconnect.
-f
- Log to file.
-g
- Use driver for Greenwich GIrBIL dongle.
-h
- Output help message.
-i
- Initiate LAP connection.
-j
- Use driver for Extended Systems JetEye dongle.
-m
- Limit maximum baud rate.
-n
- Set station name, defaults to host name.
-o
- Act as OBEX server saving objects to file.
-O
- Accept OBEX objects on socket and send them.
-p
- Use driver for Parallax LiteLink dongle.
-s
- Act as OBEX server writing objects to socket. A connection to the
specified port is opened for each OBEX object received.
-t
- Use driver for Tekram IR-210B dongle.
-v
- Set verbosity level.
-y
- Redirect stdin/stdout (used by COMM connections) to pty.
-Y
- Fork and run as daemon.
To hotsync a palm over irda, use the following commands:
irs -c -e -y /dev/ptyqf &
pilot-xfer -p /dev/ttyqf -b backup-dir
Tommy Bohlin ⟨tommy@gatespace.com⟩