Sponsored Content
Operating Systems Solaris adding memory to sun blade server ... Post 302254377 by incredible on Tuesday 4th of November 2008 08:57:27 AM
Old 11-04-2008
Well , great...
Why I asked you that question is, don't feel surprised.. Some ppl out there use a workstation as a production server, and you will know how ridiculous it will be if the system gets down..Smilie
tk cr Smilie
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Memory upgrade Sun Blade 150

I would like to upgrade the memory in my Sun Blade 150 workstation. In reading through Sun's Blade 150 DIMM Installation Guide, it indicates that the memory must be "certified by Sun for the Sun Blade 150 system." Does anyone know if any SDRAM, PC133 • CL=2 • Unbuffered • ECC • 133MHz • 3.3V ... (2 Replies)
Discussion started by: here2learn
2 Replies

2. Solaris

sun Blade 2000 and XVR100

hello, I have SunBlade 2000 with XVR-1000 graphics card. Xserver won't loaded. I've reinstalled OS 9 ( loaded Driver) nor 10 still won't do it. Anyone has this problem or have any ideas whats' wrong, greatly appreciated!! thanks in adv. (1 Reply)
Discussion started by: anphdula
1 Replies

3. Solaris

Sun Blade 100 Memory Upgrade

Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies

4. Hardware

Sun Blade T6320 memory configuration

Can you mix DIMMs in a T6320 (sparc) blade? I have read/heard that the DIMMs in a memory bay must be identical but can you have different size DIMMs installed in the blade? For instance, can you have 1 4GB DIMM in bay 0, 2 2GB DIMMs in bay 1, 4 1 GB DIMMs in bay 2 and 2 2GB DIMMs in bay 3 for a... (0 Replies)
Discussion started by: bluescreen
0 Replies

5. Solaris

Adding new hard drives on Sun SPARC T5440 server with Solaris 10

I need to add two new hard drives of 300 GB capacity to a SunSPARC T5440 server. The server currently has two hard drives of 146 GB each. How do I add the new drives to the existing UFS? What are the procedures involved in setting this server with the new hard drives? I am very new to Solaris... (6 Replies)
Discussion started by: ramatnmcc
6 Replies

6. Solaris

Sun Blade 150 not a Sun?

I have recently re-installed Solaris 10 on a Sun Blade 150 followed by a patch set (10_Recommended) dated 2011.12.05. I have just noticed /bin/sun now returns false, rather than true. See below. $ uname -a SunOS myblade1 5.10 Generic_147440-07 sun4u sparc SUNW,Sun-Blade-100 $ /bin/sparc &&... (1 Reply)
Discussion started by: apmcd47
1 Replies

7. Solaris

Memory problems in Blade 6340

We have a 6000 chassis with three blades in it. Two of the blades have "Oracle/Sun" memory in them with no complaints. The third blade is populated with Dataram dimms. That 3rd blade continues to flag a slot bad. Oracle has said they would not support the blade with Dataram memory it it. I didn't... (1 Reply)
Discussion started by: brownwrap
1 Replies

8. UNIX for Dummies Questions & Answers

SUN BLADE T6340 - which OS ?

Hi, I have server SUN BLADE T6340 and i tried install debian sparc on this machine. Will it work ? In the specification is written only Solaris 10. (4 Replies)
Discussion started by: PtaQ
4 Replies

9. Solaris

Free Sun Blade 2k, Ultra 2, Ross Hyperstation 30, cards, memory- Baltimore, MD

Hi all, My home server was Solaris for quite a while- I started with an Ultra 2 about 20 years ago, ended with a Blade 2000- but I've transitioned to Linux and am not going back. I miss the Solaris experience a bit (but not the Oracle experience), besides running with modern and small and quiet... (0 Replies)
Discussion started by: gpounce32768
0 Replies
Logcheck(8)						      System Manager's Manual						       Logcheck(8)

NAME
logcheck -- program to scan system logs for interesting lines SYNOPSIS
logcheck [OPTIONS] DESCRIPTION
The logcheck program helps spot problems and security violations in your logfiles automatically and will send the results to you periodi- cally in an e-mail. By default logcheck runs as an hourly cronjob just off the hour and after every reboot. logcheck supports three level of filtering: "paranoid" is for high-security machines running as few services as possible. Don't use it if you can't handle its verbose messages. "server" is the default and contains rules for many different daemons. "workstation" is for shel- tered machines and filters most of the messages. The ignore rules work in additive manner. "paranoid" rules are also included at level "server". "workstation" level includes both "paranoid" and "server" rules. The messages reported are sorted into three layers, system events, security events and attack alerts. The verbosity of system events is controlled by which level you choose, paranoid, server or workstation. However, security events and attack alerts are not affected by this. EXAMPLES
logcheck can be invoked directly thanks to su(8) or sudo(8), which change the user ID. The following example checks the logfiles without updating the offset and outputs everything to STDOUT. sudo -u logcheck logcheck -o -t OPTIONS
A summary of options is included below. -c CFG Overrule default configuration file. -d Debug mode. -h Show usage information. -H Use this hostname string in the subject of logcheck mail. -l LOG Run logfile through logcheck. -L CFG Overrule default logfiles list. -m Mail report to recipient. -o STDOUT mode, not sending mail. -p Set the report level to "paranoid". -r DIR Overrule default rules directory. -R Adds "Reboot:" to the email subject line. -s Set the report level to "server". -S DIR Overrule default state directory. -t Testing mode does not update offset. -T Do not remove the TMPDIR. -u Enable syslog-summary. -v Print current version. -w Set the report level to "workstation". FILES
/etc/logcheck/logcheck.conf is the main configuration file. /etc/logcheck/logcheck.logfiles is the list of files to monitor. /usr/share/doc/logcheck-database/README.logcheck-database.gz for hints on how to write, test and maintain rules. EXIT STATUS
0 upon success; 1 upon failure SEE ALSO
logtail(8) AUTHOR
logcheck is developed by Debian logcheck Team at alioth: http://alioth.debian.org/projects/logcheck/. This manual page was written by Jon Middleton. Logcheck(8)
All times are GMT -4. The time now is 08:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy