11-16-2015
I installed both those update and I believe OSS711e did the trick. I guess I should pay attention when they say "critical". Got ahead of myself trying to see if this machine would work. I will spend the rest of the evening loading the rest of the patches and updates :-). In answer to your question it's an ASUS motherboard with an I7-3770. I know old but still newer than what they have now. Thank you so much for your help, it is greatly appreciated!!! Jim
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work
i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies
2. Filesystems, Disks and Memory
Hello all,
I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies
3. UNIX for Dummies Questions & Answers
My company has a Compaq NeoServer running SCO OpenServer Release 5 (vintage late 1998) that we inherited from another small company. This has been a very reliable file server for our small company. We recently installed a new Linux server and would like to convert the NeoServer to other functions... (1 Reply)
Discussion started by: Jeff Boyce
1 Replies
4. UNIX for Dummies Questions & Answers
I am running the beta version of Openserver by SCO and the
Graphical login only gives me the option of logging into the
system v xwindows and I know that this build included KDE 3.3
I have tried the kde kdm command at shell prompt: command not
found. Any ideas anyone? (0 Replies)
Discussion started by: coreykirk
0 Replies
5. UNIX for Dummies Questions & Answers
Hi guys
I installed this new server with 5.0.7 openserver and i'm getting a lot of this process, if a stop and restart the printer spooler they go away but after a few minutes they appear again.This is how it looks like.
root 372 615 0 - - 00:00:00 <defunct>
root ... (0 Replies)
Discussion started by: josramon
0 Replies
6. SCO
Hi everyone,
We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies
7. SCO
we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached).
At the time of installation we link both driver BTLD
Boot: Defbootstr link=accraid ad320
Aftes succesfully installation of accraid btld... (6 Replies)
Discussion started by: hafizurr
6 Replies
8. SCO
can not for the life of me workout which BTLD to load allways shows no HDD available can any one give me a clue
tried
hpsas
aacraid
lsil
a160
a320
server is a ML310 G4 ?????:confused::confused: (7 Replies)
Discussion started by: wildginger
7 Replies
9. SCO
Hi
I m trying to install SCo 5.0.5 on my laptop but it fails, I was able to install it on another computer and it did work, but with this IBM LENOVO R61 Laptop, it is giving me the message Memory error loading kernel, I searched the net concerning this issue and found that i have to write this... (1 Reply)
Discussion started by: bashar_smeirat
1 Replies
10. SCO
I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system.
Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System... (2 Replies)
Discussion started by: jesmith
2 Replies
LEARN ABOUT DEBIAN
sys::utmp::utent
Sys::Utmp::Utent(3pm) User Contributed Perl Documentation Sys::Utmp::Utent(3pm)
NAME
Sys::Utmp::Utent - represent a single utmp entry
SYNOPSIS
use Sys::Utmp;
my $utmp = Sys::Utmp->new();
while ( my $utent = $utmp->getutent() )
{
if ( $utent->user_process )
{
print $utent->ut_user,"
";
}
}
$utmp->endutent;
DESCRIPTION
As described in the Sys::Utmp documentation the getutent method returns an object of the type Sys::Utmp::Utent which provides methods for
accessing the fields in the utmp record. There are also methods for determining the type of the record.
The access methods relate to the common names for the members of the C struct utent - those provided are the superset from the Gnu
implementation and may not be available on all systems: where they are not they will return the empty string.
ut_user
Returns the use this record was created for if this is a record for a user process. Some systems may return other information
depending on the record type. If no user was set this will be the empty string. If tainting is switched on with the '-T' switch to
perl then this will be 'tainted' as it is possible that the user name came from an untrusted source.
ut_id
The identifier for this record - it might be the inittab tag or some other system dependent value.
ut_line
For user process records this will be the name of the terminalor line that the user is connected on.
ut_pid
The process ID of the process that created this record.
ut_type
The type of the record this will have a value corresponding to one of the constants (not all of these may be available on all systems
and there may well be others which should be described in the getutent manpage or in /usr/include/utmp.h ) :
ACCOUNTING - record was created for system accounting purposes.
BOOT_TIME - the record was created at boot time.
DEAD_PROCESS - The process that created this record has terminated.
EMPTY - record probably contains no other useful information.
INIT_PROCESS - this is a record for process created by init.
LOGIN_PROCESS - this record was created for a login process (e.g. getty).
NEW_TIME - record created when the system time has been set.
OLD_TIME - record recording the old tme when the system time has been set.
RUN_LVL - records the time at which the current run level was started.
USER_PROCESS - record created for a user process (e.g. a login )
for convenience Sys::Utmp::Utent provides methods which are lower case versions of the constant names which return true if the record
is of that type.
ut_host
On systems which support this the method will return the hostname of the host for which the process that created the record was started
- for example for a telnet login. If taint checking has been turned on (with the -T switch to perl ) then this value will be tainted
as it is possible that a remote user will be in control of the DNS for the machine they have logged in from. ( see perlsec for more on
tainting )
ut_time
The time in epoch seconds wt which the record was created.
BUGS
Probably. This module has been tested on Linux, Solaris, FreeBSD ,SCO Openserver and SCO UnixWare and found to work on those platforms.
If you have difficulty building the module or it doesnt behave as expected then please contact the author including if appropriate your
/usr/include/utmp.h
AUTHOR
Jonathan Stowe, <jns@gellyfish.com>
LICENCE
This Software is Copyright Jonathan Stowe 2001-2006
This Software is published as-is with no warranty express or implied.
This is free software and can be distributed under the same terms as Perl itself.
SEE ALSO
perl. Sys::Utmp::Utent
perl v5.14.2 2006-10-13 Sys::Utmp::Utent(3pm)