Sponsored Content
Operating Systems OS X (Apple) [launchd] Creating a basic firewall Post 302376093 by tlarkin on Monday 30th of November 2009 03:48:29 PM
Old 11-30-2009
Yeah looking into it further it seems a lot trickier than just a straight forward script....
 

5 More Discussions You Might Find Interesting

1. OS X (Apple)

interval in a launchd script

Hi, i'm planning a to automate my backup with a rsync user deamon in my launchd and let that run every 2 hours. my server contains a lot of video data which can expand rapidly , up to 1TB, in an interval of 2 hours. now i'm wondering what will happen when a rsync is running longer then the... (1 Reply)
Discussion started by: wessel
1 Replies

2. Programming

Creating a basic UNIX shell script for chatting

Hey guys, This is quite simply what I'm trying to make: A program that runs in a UNIX terminal that you can output text messages to from another machine. These text messages would be prepended with a customized prompt. I'd also like to have the window spew out random dumps of flavor text not... (1 Reply)
Discussion started by: AcerAspirant
1 Replies

3. UNIX for Dummies Questions & Answers

Launchd-owned processes unexpected behavior

Ok, so I have been struggling with this for a few days and I think I need an explanation of a few things before I go any further. I'm not sure it's possible to do what I'm trying, so before I pull my hair out, here is what I'm doing: I have written a program in LiveCode that sits on our... (2 Replies)
Discussion started by: nextyoyoma
2 Replies

4. Shell Programming and Scripting

Expect command when triggered by launchd

Hi folks, Im having trouble with an expect command in a shell script I use to back up mac os x servers. This one is being run on a 10.8.2 Server as part of a larger bash script. The script executes perfectly all the way through when triggered on the command line, but when launchd triggers it at... (4 Replies)
Discussion started by: rowie718
4 Replies

5. IP Networking

iptables nat/masquerade - how to act as a basic firewall?

edit: SOLVED - see below for solution Hi there, I've inherited a gob of Linux hosts and so am learning linux from the bottom of the deep end of the pool (gotta say I'm warming up to Linux though - it's not half bad) Right now iptables is confusing me and I could use some pointers as to how... (0 Replies)
Discussion started by: Smiling Dragon
0 Replies
dot-forward(1)						      General Commands Manual						    dot-forward(1)

NAME
dot-forward - read a .forward file under qmail SYNOPSIS
in ~/.qmail: | dot-forward [ -nN ] file ... OVERVIEW
dot-forward forwards incoming messages according to sendmail-style instructions in file, if file exists. Normally file is .forward. WARNING: If you create a .qmail file to enable dot-forward, make sure to add a second line specifying delivery to your normal mailbox. For example: |dot-forward .forward ./Mailbox COMPATIBILITY WARNING: dot-forward does not support :include: or mbox deliveries. You can use the delivery mechanism described in dot- qmail(5) instead. OPTIONS
-N (Default.) Read and forward a message. -n Parse file and print the forwarding instructions in it, one per line; do not follow the instructions. You can use this option from the command line to see how your .forward file will be interpreted: dot-forward -n .forward FILE HANDLING
When a message arrives, dot-forward opens file and handles it as discussed below. It exits 99, so qmail-local will ignore further instruc- tions in .qmail. Exception: If file specifies delivery directly to you, dot-forward exits 0, so qmail-local will read further instructions in .qmail. If file does not exist, dot-forward exits 0. You can list several files; then dot-forward will try each one in turn, using the first one that exists, or exiting 0 if none exist. COMPATIBILITY WARNING: dot-forward treats an empty file as if it did not exist. Versions of sendmail before V8 would throw away the incom- ing message. COMPATIBILITY WARNING: If dot-forward encounters a temporary error opening file, it exits 111, so that qmail-local will try again later. sendmail assumes incorrectly that file does not exist. COMPATIBILITY WARNING: file must be readable by dot-forward, which is normally running as the user. sendmail places different constraints on its .forward permissions, since it is normally running as root. FORWARDING
Normally file contains an address. dot-forward forwards the message to that address. The address is parsed as if it were in an RFC 822 message header. Parenthesized comments and bracketed addresses are permitted: bob (Bob, the postmaster) @heaven.af.mil Addresses with special characters must be quoted: "spaced out mailbox"@heaven.af.mil Address groups are not permitted. file can contain any number of lines, each line containing any number of addresses. dot-forward forwards the message to each address: bob, fred, susan Joe Shmoe <shmoe@heaven.af.mil> An address without a fully qualified domain name is handled as described in qmail-header(5). Exception: Certain addresses without domain names are handled specially, as described below. DIRECT DELIVERY
If an address does not contain a domain name, and matches the environment variable $USER (without regard to case), it specifies delivery directly to you. If an address matches $USER@$HOST (without regard to case), it specifies delivery directly to you. COMPATIBILITY WARNING: sendmail's handling of quotes and backslashes violates RFC 821 and RFC 822, and is not supported by dot-forward. dot-forward treats joe the same way as joe. The dot-qmail delivery mechanism lets each user manage several addresses, so there is no need for a special syntax to get around forwarding. COMMANDS
If an address does not contain a domain name, and begins with a vertical bar, dot-forward takes the rest of the address as a command to run: bob, "|vacation bob" dot-forward feeds the message to the command, preceded by the environment variables $UFLINE, $RPLINE, and $DTLINE. COMPATIBILITY WARNING: Internet addresses can legitimately start with a slash or vertical bar. dot-forward treats anything with an unquoted @ as an address. sendmail appears to have various problems coping with these addresses, and with commands that contain @ signs. COMMENTS
Any line in file that begins with # is ignored: # this is a comment COMPATIBILITY WARNING: Versions of sendmail before V8 did not allow comments in .forward files. VERSION
This is dot-forward 0.71. The dot-forward home page is http://pobox.com/~djb/dot-forward.html. SEE ALSO
qmail-header(5), dot-qmail(5) dot-forward(1)
All times are GMT -4. The time now is 10:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy