7 More Discussions You Might Find Interesting
1. Red Hat
removing the post (6 Replies)
Discussion started by: titanic4u
6 Replies
2. Linux
Hi Team,
I have joined the Suse Linux Server in my domain. I am not able update the DNS but I am able to join the domain. net ads testjoin gives me Join ok.
even net ads dns register -P results to DNS update failed.
wbinfo -u and wbinfo -g also not working.
Samba Configuration:
... (1 Reply)
Discussion started by: naree
1 Replies
3. UNIX for Dummies Questions & Answers
I cannot access the Accounts Manager facility when using SCO (F2 Screen) or scoadmin from the Command prompt. when using System Administration screen the Error "Unable to get initial list of users" is given. (0 Replies)
Discussion started by: Waitstejo
0 Replies
4. HP-UX
Hi Friends
We have two node trucluster Tru64 4.0F Alpha Servers,In one of Tru64 4.0F Unix Server I am unable to unlock users, when I issue usermod command I will get following error
/usr/sbin/usermod -x administrative_lock_applied=0 username
account manager has exited unexpectedly - please... (0 Replies)
Discussion started by: madanmb
0 Replies
5. UNIX for Dummies Questions & Answers
rm: Unable to remove directory /mnt/users/test/logs/: File exists
ls -latr
total 191208
drwxrwxrwx 6 test echo 4096 Jul 3 22:36 ..
-rwxrwxrwx 1 test echo 97692804 Jul 3 22:36 .nfsDFA4
drwxrwxr-x 2 test echo 4096 Jul 3 23:00 .
M not able to delete... (4 Replies)
Discussion started by: solitare123
4 Replies
6. SCO
UnixWare 7, Release 7.1.3
We have a customer that has frequent issues with Non-Root users being unable to print. They are able to print w/o issues, but all of the sudden it stops working. The only workaround we have at this point is to reboot the server. It is happening weekly according to... (1 Reply)
Discussion started by: cfshd
1 Replies
7. Shell Programming and Scripting
I'm looking for a script that allows me to export to CSV, the information I need. Somehow, I must gather the User ID, the User Login, the Last User Login, the Password complexity, the Password Age, The Expiration Date, . . .
My experience is equal to very, very few.
The only thing I have is... (2 Replies)
Discussion started by: catfish
2 Replies
logger(1) General Commands Manual logger(1)
NAME
logger - Makes entries in the system log
SYNOPSIS
/usr/bin/logger [-f file] [-i] [-p[facility.]priority] [-t tag] [message...]
logger [-b] [message...]
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
logger: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
[Tru64 UNIX] Logs the informational message to the binary event logger instead of the syslog() subroutine and enters information in the
binary event log file. The uerf command with the -r 250 option reports the informational messages that are in the binary event log file,
which is used for system maintenance and troubleshooting. The -b option cannot be used with any other options. [Tru64 UNIX] Logs all
lines in file. [Tru64 UNIX] Logs the process ID (PID) of the logger process with each line. [Tru64 UNIX] Enters the message with the
specified priority and, if specified, from the specified facility.
[Tru64 UNIX] You can specify priority as either an alphabetic string or its integer equivalent. You can specify the following val-
ues for the priority variable: [Tru64 UNIX] (0) [Tru64 UNIX] The system is unusable. (0) [Tru64 UNIX] Action must be taken imme-
diately. (1) [Tru64 UNIX] Critical conditions. (2) [Tru64 UNIX] Error conditions. (3) [Tru64 UNIX] (3) [Tru64 UNIX] (4)
[Tru64 UNIX] Warning conditions. (4) [Tru64 UNIX] Normal but significant condition. (5) [Tru64 UNIX] Informational. (6) [Tru64
UNIX] Debug-level messages. (7)
[Tru64 UNIX] You can also specify a value for the facility variable, which indicates the source of the event. You can specify
facility as either an alphabetic string or its integer equivalent. The integer values appear in parentheses. You can specify the
following values for the facility variable: [Tru64 UNIX] Kernel messages. (0) [Tru64 UNIX] Random user-level messages. (8) [Tru64
UNIX] Mail system. (16) [Tru64 UNIX] System daemons. (24) [Tru64 UNIX] Security/authorization messages. (32) [Tru64 UNIX] (32)
[Tru64 UNIX] Messages syslogd generates internally. (40) [Tru64 UNIX] Line printer subsystem. (48) [Tru64 UNIX] Network news
subsystem. (56) [Tru64 UNIX] UUCP subsystem. (64) [Tru64 UNIX] Clock daemon. (72) [Tru64 UNIX] (128) [Tru64 UNIX] (136)
[Tru64 UNIX] (144) [Tru64 UNIX] (152) [Tru64 UNIX] (160) [Tru64 UNIX] (168) [Tru64 UNIX] (176) [Tru64 UNIX] (184) [Tru64
UNIX] Precedes each entry in the log with tag.
OPERANDS
You can specify the message to be used for entries on the command line or with the -f file option, which specifies that each line in file
be logged as an entry. If you do not specify message or -f, logger reads standard input.
DESCRIPTION
The logger command makes the specified entries in the system log file.
The logger command provides a program and shell script interface to the syslog() subroutine. The file in which entries are made depends on
the current system log configuration; see syslog and syslogd for more information.
NOTES
The effects of the environment variable LC_MESSAGES apply only to diagnostic messages generated by logger, and not to any messages written
by the use of the command.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
EXAMPLES
To log the system reboot, including the process ID of the process running logger, enter: logger -i System rebooted To log each line in the
file build.events with the tag trial build preceding them, enter: logger -f build.events -t "trial build" The following commands are equiv-
alent and enter events of warning priority to the log: logger -p warning
logger -p 4 The following commands are equivalent and enter events from the daemon facility of warning priority: logger -p daemon.warning
logger -p 24.4 To specify the debug priority with a priority name, enter: logger -p debug my message
To specify the debug priority with a priority number, enter: logger -p 7 my message To specify both debug priority and the user
facility, enter: logger -p user.debug my message
To specify the same facility/priority pair using numeric values, enter: logger -p 8.7 my message
You can also combine alphabetic and numeric specifications: logger -p user.7 my message logger -p 8.debug my message
ENVIRONMENT VARIABLES
The following environment variables affect the execution of logger: Provides a default value for the internationalization variables that
are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization
variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string
value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of
bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments). Determines the locale for
the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing
of LC_MESSAGES.
SEE ALSO
Commands: binlogd(8), syslogd(8), uerf(8)
Functions: syslog(3)
Standards: standards(5)
logger(1)