Sponsored Content
Full Discussion: Are the BSDs dying?
The Lounge What is on Your Mind? Are the BSDs dying? Post 303012247 by dodona on Thursday 1st of February 2018 05:14:38 AM
Old 02-01-2018
Quote:
Originally Posted by Corona688
Has it ever been wildly popular? It's been influential but that's not the same thing.
.
see the BSD of the late 70ths/80ths has a lot more to do with *NIX as we know it today than AT&T who adopted a lot from BSD for System III and V. TCP,Internet, virtual memory, video terminal, vi/ex, reliable signals, job control and even printer queues, just to name a few, are all genuine BSD inventions.
 

7 More Discussions You Might Find Interesting

1. Ubuntu

Internet dying in Debian?

For some reason after a while my internet connection dies. I just moved on to Debian from Ubuntu and I can't find the dhclient-program to reconfigure dhcp. Pretty new to *nix's. ONe thing I noticed while rebooting (do get my connection back) is that it configures dhcp and says: reconfigure (or... (1 Reply)
Discussion started by: riwa
1 Replies

2. IP Networking

network connection dying after an uptime of a day or two days

hie guys I am running fedora 6 on remote machines which are connecting to my server. The remote machines connect through one machine (more like my router) to the server. The problem i am having is that the remote machines are suppose to be reporting in real time mode to the server. Most of these... (2 Replies)
Discussion started by: no3more
2 Replies

3. Boot Loaders

EFI on BSDs problem

Hi, at time I have some problems installing a BSD system on my GPT disk... Thing is, I don't understand why support for the EFI seems to be so hard. Neither FreeBSD nor NetBSD nor OpenBSD seem to be able to install on GPT disks. They all misconceive the hard disk would use an MBR and the DOS... (6 Replies)
Discussion started by: Blackbird
6 Replies

4. Programming

Java application dying randomly

Hi, (First post, please be gental!) I have a java app that I am running on unix (centos) But it keeps dying randomly. The times seem random from anything between 3 hours and 3 days. I have a cronjob running to restart it when ever it dies but I would rather this happened less often. ... (2 Replies)
Discussion started by: sm9ai
2 Replies

5. Shell Programming and Scripting

Expect script cronjob running but dying prematurely

I have an Ubuntu machine that I'd like to update automatically. I've written an expect script to run the aptitude package manager and update my packages. Essentially it does: aptitude update && aptitude upgrade while answering "yes" at the appropriate time. It works quite nicely when run... (4 Replies)
Discussion started by: CluelessPerson
4 Replies

6. Shell Programming and Scripting

Utilities not dying after script run

Hi folks, Friendly router geek wanting to be a programmer here... So I worked with another guy here and came up with this to capture Unix admin data: #!/bin/ksh # # # Set Default Paths # PATH=/usr/apps/client/bin:$PATH; export PATH... (4 Replies)
Discussion started by: Marc G
4 Replies

7. Red Hat

Snmpd dying on centos7.1

Hello All, SNMPD dying after 2 mins once it started. Here is the configuration Oct 12 04:43:00 localhost systemd: Starting Simple Network Management Protocol (SNMP) Daemon.... Oct 12 04:43:00 localhost snmpd: dlopen failed: /usr/lib64/libcmaX64.so: cannot open shared object file: No such... (1 Reply)
Discussion started by: shekar777
1 Replies
GETPGRP(2)						      BSD System Calls Manual							GETPGRP(2)

NAME
getpgid, getpgrp -- get process group LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <unistd.h> pid_t getpgid(pid_t pid); pid_t getpgrp(void); DESCRIPTION
The process group of the current process is returned by getpgrp(). The process group of the process identified by pid is returned by getpgid(). If pid is zero, getpgid() returns the process group of the current process. Process groups are used for distribution of signals, and by terminals to arbitrate requests for their input: processes that have the same process group as the terminal are foreground and may read, while others will block with a signal if they attempt to read. This call is thus used by programs such as csh(1) to create process groups in implementing job control. The tcgetpgrp() and tcsetpgrp() calls are used to get/set the process group of the control terminal. RETURN VALUES
The getpgrp() call always succeeds. Upon successful completion, the getpgid() call returns the process group of the specified process; oth- erwise, it returns a value of -1 and sets errno to indicate the error. ERRORS
getpgid() will succeed unless: [ESRCH] There is no process whose process ID equals pid. SEE ALSO
getsid(2), setpgid(2), termios(4) HISTORY
The getpgrp() function call appeared in 4.0BSD. The getpgid() function call is derived from its usage in System V Release 4. STANDARDS
The getpgrp() function call is expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1''). COMPATIBILITY
This version of getpgrp() differs from past Berkeley versions by not taking a pid_t pid argument. This incompatibility is required by ISO/IEC 9945-1:1990 (``POSIX.1''). From the ISO/IEC 9945-1:1990 (``POSIX.1'') Rationale: 4.3BSD provides a getpgrp() function that returns the process group ID for a specified process. Although this function is used to support job control, all known job-control shells always specify the calling process with this function. Thus, the simpler AT&T System V UNIX getpgrp() suffices, and the added complexity of the 4.3BSD getpgrp() has been omitted from POSIX.1. The old functionality is available from the getpgid() function. BSD
June 4, 1993 BSD
All times are GMT -4. The time now is 03:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy