Sponsored Content
Full Discussion: Messages
Top Forums Shell Programming and Scripting Messages Post 302453042 by sonu_pal on Tuesday 14th of September 2010 12:17:21 AM
Old 09-14-2010
Messages

hi all,

If we do not want to be disturbed by messages from other users while we are working, what would we do ?
can anyone just help me..
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

error messages in /var/adm/messages

Hi, I have a SunFire V490, Solaris 10 with XP1024 storage and HP Library. I have noticed the following error messages in the /var/adm/messages file. These errors are being generated constantly. Also commands like devfsadm, format cfgadm etc are getting hung. After a reboot it works fine for a... (1 Reply)
Discussion started by: nitinp82
1 Replies

2. Solaris

Info req: /var/adm/messages - Kern.warning - different ID messages

Hi all, where I can find a list and meaning of the ID number (for example ID 353554 kern.warning)? Thanks in advance Pierluigi (1 Reply)
Discussion started by: Petrucci
1 Replies

3. Solaris

Help understanding [daemon.warning] messages in /var/adm/messages

Hi I've been using solaris for a few days now. During the install process i had some problems configuring my nic as i needed to install a third-party driver, which i got from a a linked site from the Sun Device Detector tool a ran prior to installing. I got it working eventually, but i'm... (1 Reply)
Discussion started by: jpg.2009
1 Replies

4. Solaris

[kern.warning] messages in /var/adm/messages

Hi Having looked through the log file /var/adm/messages i've noticed these kernel warning messages and i don't know what they mean: !-- @page { size: 8.5in 11in; margin: 0.79in } P { margin-bottom: 0.08in } --> cpudrv: NOTICE: cpu_acpi: _TSS package not found. cpudrv: WARNING:... (1 Reply)
Discussion started by: jpg.2009
1 Replies

5. Solaris

uamod messages in /var/adm/messages

Hello, I am using Solaris 10 and I'm geting the folowing error in /var/adm/messages. Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) set threshold to default values Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) threshold values... (4 Replies)
Discussion started by: toshibelul
4 Replies

6. UNIX for Dummies Questions & Answers

fprintd messages in /var/log/messages

Whenever a user uses su I get the following error messages in /var/log/messages: Nov 23 04:24:55 <REMOVED> abrt: saved core dump of pid 26141 (/usr/libexec/fprintd) to /var/spool/abrt/ccpp-1322018695-26141.new/coredump (753664 bytes) Nov 23 04:24:55 <REMOVED> abrtd: Directory... (3 Replies)
Discussion started by: JakesHat
3 Replies

7. UNIX for Dummies Questions & Answers

Why there are /var/adm/messages.0,messages.1,messages.2,messages.3

Hi folks, In what circumstance does the log move to /var/adm/messages.0.......messages.1,messages.2,messages.3 .......etc ---------- Post updated at 06:23 PM ---------- Previous update was at 06:17 PM ---------- To make my questions more understandable, What are the processes that... (4 Replies)
Discussion started by: kimurayuki
4 Replies

8. SuSE

Some error messages in var/log/messages

How are you? SUSE V10 and 11. In /var/log/messages I see these lines in some servers. I'd like to know what causes these errors and how to fix them. Thank you, error: PAM: Authentication failure for root from XXXXXXXX Did not receive identification string from XXXXXXX Invalid user suse-gm... (2 Replies)
Discussion started by: JDBA
2 Replies

9. Solaris

Local zone is not logging systems messages to /var/adm/messages

This is isolated to just 1 non-global zone out of many zones managed This is a Solaris 11 system on SPARC This is NOT a branded zone syslogd is active This came to our attention when one of our scripts didn't run over the weekend prompting us to check our messages logging in... (6 Replies)
Discussion started by: samthewildone
6 Replies
MSGS(1) 						      General Commands Manual							   MSGS(1)

NAME
msgs - system messages and junk mail program SYNOPSIS
msgs [ -fhlpq ] [ number ] [ -number ] msgs -s msgs -c [ -days ] DESCRIPTION
Msgs is used to read system messages. These messages are sent by mailing to the login `msgs' and should be short pieces of information which are suitable to be read once by most users of the system. Msgs is normally invoked each time you login, by placing it in the file .login (.profile if you use /bin/sh). It will then prompt you with the source and subject of each new message. If there is no subject line, the first few non-blank lines of the message will be displayed. If there is more to the message, you will be told how long it is and asked whether you wish to see the rest of the message. The possible responses are: y type the rest of the message. RETURN synonym for y. n skip this message and go on to the next message. - redisplay the last message. q drops you out of msgs; the next time you run the program it will pick up where you left off. s append the current message to the file ``Messages'' in the current directory; `s-' will save the previously displayed message. A `s' or `s-' may be followed by a space and a file name to receive the message replacing the default ``Messages''. m or `m-' causes a copy of the specified message to be placed in a temporary mailbox and mail(1) to be invoked on that mailbox. Both `m' and `s' accept a numeric argument in place of the `-'. Msgs keeps track of the next message you will see by a number in the file .msgsrc in your home directory. In the directory /usr/msgs it keeps a set of files whose names are the (sequential) numbers of the messages they represent. The file /usr/msgs/bounds shows the low and high number of the messages in the directory so that msgs can quickly determine if there are no messages for you. If the contents of bounds is incorrect it can be fixed by removing it; msgs will make a new bounds file the next time it is run. The -s option is used for setting up the posting of messages. The line msgs: "| /usr/ucb/msgs -s" should be include in /etc/aliases to enable posting of messages. The -c option is used for performing cleanup on /usr/msgs. An entry with the -c option should be placed in /etc/crontab to run every night. This will remove all messages over 21 days old. A different expiration may be specified on the command line to override the default. Options when reading messages include: -f which causes it not to say ``No new messages.''. This is useful in your .login file since this is often the case here. -q Queries whether there are messages, printing ``There are new messages.'' if there are. The command ``msgs -q'' is often used in login scripts. -h causes msgs to print the first part of messages only. -l option causes only locally originated messages to be reported. num A message number can be given on the command line, causing msgs to start at the specified message rather than at the next message indicated by your .msgsrc file. Thus msgs -h 1 prints the first part of all messages. -number will cause msgs to start number messages back from the one indicated by your .msgsrc file, useful for reviews of recent messages. -p causes long messages to be piped through more(1). Within msgs you can also go to any specific message by typing its number when msgs requests input as to what to do. FILES
/usr/msgs/* database ~/.msgsrc number of next message to be presented AUTHORS
William Joy David Wasley SEE ALSO
aliases(5), crontab(5), mail(1), more(1) BUGS
4th Berkeley Distribution October 22, 1996 MSGS(1)
All times are GMT -4. The time now is 05:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy