Sponsored Content
Full Discussion: firewalls and proxys
Special Forums Cybersecurity firewalls and proxys Post 14802 by Neo on Wednesday 6th of February 2002 04:35:46 PM
Old 02-06-2002
LivinFree, thanks for your posts. Your are absolutely right. Much appreciated! -Neo
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Linux Firewalls

I've been considering switching my companies production firewall from FreeBSD and OpenBSD to Linux. The reason being is having so many different flavors of Unix on our production network from FreeBSD, OpenBSD, Solaris, and Linux makes things more difficult to manage from a standardized... (2 Replies)
Discussion started by: mstevenson
2 Replies

2. IP Networking

Halted Firewalls by Mike Murray

Secure packet filtering on high-bandwidths fw/rtr for large business tasks. Has anyone tried this concept on openbsd? The article is posted at www.sysadminmag.com on page 27. January 2002 issue. I believe Mike has hit upon something that can be applied in the field today and prevent fw... (0 Replies)
Discussion started by: dpatel
0 Replies

3. UNIX for Dummies Questions & Answers

Firewalls and other security measures...

One day, while using my PC with Windows XP, my router just stopped working. So, for the ability to connect to the web at that moment, I connected directly to the cable modem without my router. I noticed immediately that people were trying to hack into my computer because my personal firewall would... (2 Replies)
Discussion started by: Minnesota Red
2 Replies

4. UNIX for Advanced & Expert Users

Firewalls

Hi, I was doing abit of reading on firewalls when this question came up. Is there any command which sets up a firewall that will only allow packets through if they come from a port number less than 1024? How about a command which allows packets through if they are destined for a port... (3 Replies)
Discussion started by: sleepster
3 Replies

5. Cybersecurity

Firewalls and cryptography

As we know, firewall is designed to keep unauthorized outsiders from tampering with a computer system or network. We don't talk about computer security without cryptography. In this case, may I know,How does cryptographic protection (at the TCP/IP layers or at the application layer) affect a... (1 Reply)
Discussion started by: heroine
1 Replies
PSIGNAL(9)						   BSD Kernel Developer's Manual						PSIGNAL(9)

NAME
psignal, pgsignal, gsignal -- post signal to a process or process group SYNOPSIS
#include <sys/types.h> #include <sys/signalvar.h> void psignal(struct proc *p, int signum); void pgsignal(struct pgrp *pgrp, int signum, int checkctty); void gsignal(int pgid, int signum); DESCRIPTION
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the process represented by the process structure p. With a few exceptions noted below, the target process signal disposition is updated and is marked as runnable, so further handling of the signal is done in the context of the target process after a context switch. Note that psignal() does not by itself cause a context switch to happen. The target process is not marked as runnable in the following cases: o The target process is sleeping uninterruptibly. The signal will be noticed when the process returns from the system call or trap. o The target process is currently ignoring the signal. o If a stop signal is sent to a sleeping process that takes the default action (see sigaction(2)), the process is stopped without awakening it. o SIGCONT restarts a stopped process (or puts them back to sleep) regardless of the signal action (e.g., blocked or ignored). If the target process is being traced psignal() behaves as if the target process were taking the default action for signum. This allows the tracing process to be notified of the signal. The pgsignal() function posts signal number signum to each member of the process group described by pgrp. If checkctty is non-zero, the sig- nal will be posted only to processes that have a controlling terminal. pgsignal() is implemented by walking along the process list headed by the field pg_members of the process group structure pointed at by pgrp and calling psignal() as appropriate. If pgrp is NULL no action is taken. The gsignal() function posts signal number signum to each member of the process group identified by the group id pgid. gsignal() first finds the group structure associated with pgid, then invokes pgsignal() with the argument checkctty set to zero. If pgid is zero no action is taken. SEE ALSO
sigaction(2), signal(9), tsleep(9) BSD
June 22, 1996 BSD
All times are GMT -4. The time now is 01:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy