Are the BSDs dying? Post: 303012247

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...

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...

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...

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. ...

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...

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...

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...

LEARN ABOUT FREEBSD

lock

LOCK(1) 						    BSD General Commands Manual 						   LOCK(1)

NAME

     lock -- reserve a terminal

SYNOPSIS

     lock [-npv] [-t timeout]

DESCRIPTION

     The lock utility requests a password from the user, reads it again for verification and then will normally not relinquish the terminal until
     the password is repeated.	There are two other conditions under which it will terminate: it will timeout after some interval of time and it
     may be killed by someone with the appropriate permission.

     The following options are available:

     -n      Do not use a timeout value.  Terminal will be locked forever.

     -p      A password is not requested, instead the user's current login password is used.

     -t timeout
	     The time limit (default 15 minutes) is changed to timeout minutes.

     -v      Disable switching virtual terminals while this terminal is locked.  This option is implemented in a way similar to the -S option of
	     vidcontrol(1), and thus has the same restrictions.  It is only available if the terminal in question is a syscons(4) or vt(4) virtual
	     terminal.

SEE ALSO

     vidcontrol(1), syscons(4), vt(4)

HISTORY

     The lock command appeared in 3.0BSD.

BSD
								   July 10, 2002							       BSD