03-01-2011
You cannot change the location, it is coded into svc.startd and not configurable. All Logfiles will be created in the same location. The name of the logfile is derived from the service fmri.
9 More Discussions You Might Find Interesting
1. HP-UX
Can anyone tell me how I can change the default location for a netbackup installation to another location on my box? The default location is too small and I want to install in another location that has the adequate space. The Netbackup user manual is USELESS!!:mad::mad: (3 Replies)
Discussion started by: impunchdrunk
3 Replies
2. Infrastructure Monitoring
Hi,
I need to kill processes from a specific location for Linux, HP, AIX and Solaris.
My problem is to be able to identify the location of the running processes.
I've tried with a simple "ps -fu username | grep mylocation" but if the process command has been run directly from the location,... (2 Replies)
Discussion started by: Peuj
2 Replies
3. UNIX for Dummies Questions & Answers
Hello,
Is it possible to make a file manager use different "colored folders" when browsing specific directories?
For example, if I open a gnome file manager and browse my windows share at, smb://192.168.1.101/z/ , can I make those folders appear green?
And when I open another instance of... (0 Replies)
Discussion started by: bz43
0 Replies
4. UNIX for Advanced & Expert Users
Thanks in advance.
My environment is Ubuntu 9.04 desktop customized to be a high school classroom server for teaching code development. I have a unique "fake" jail called "lshell" which is very easy to setup and restricts users to commands that I dictate DISALLOWING ANYTHING ELSE. These... (6 Replies)
Discussion started by: tuxhats
6 Replies
5. Solaris
I can't get the exact error message because I am at home, but on Solaris 10u5 machine I have at work, a few services are stuck in the maintenance state with the following error message in the individual service logs (/var/svc/log/FMRI:instance.log):
Cannot chdir: permission denied
Fortunately... (2 Replies)
Discussion started by: ilikecows
2 Replies
6. Solaris
I'm running Tibco Hawk (hawkhma and agent) on a number of solaris 10 boxes (both x86 and Sparc).
Tibco Hawk is a monitoring system, that can monitor processs and logs on the OS and applications. It also have the ability to start a process, if it for some reason, have died.
I have implemented... (2 Replies)
Discussion started by: u_paludan
2 Replies
7. UNIX for Dummies Questions & Answers
avahi error message goes to /var/log/messages , how can put avahi to log the error in a file /var/log/avahi-error instead of /var/log/messages (1 Reply)
Discussion started by: prpkrk
1 Replies
8. Solaris
I found that there was a SMF log file: /var/svc/log/milestone-multi-user-server:default.log.0 which occupied around 19G bytes.
Please help me how to purge this massive file.
Can I just use cat /dev/null > /var/svc/log/milesto..... to this file without any interruption to a non-stop system?... (11 Replies)
Discussion started by: AlexLi
11 Replies
9. UNIX for Beginners Questions & Answers
Hi ALL,
I am trying to find the installed tomcat version and location of the server.xml file to get the tomcat port number.
Using below script to do that.
#!/usr/bin/env bash
var1=$(find / -name "version.sh" ! -size 0 2>&1 |egrep -v "tmp|docker")
for loc1 in $var1
do
... (1 Reply)
Discussion started by: sravani25
1 Replies
LEARN ABOUT OPENSOLARIS
autofs
autofs(4) File Formats autofs(4)
NAME
autofs - file containing parameter values for automountd daemon and automount command
SYNOPSIS
/etc/default/autofs
DESCRIPTION
The autofs file resides in directory /etc/default and supplies default parameters for the automountd(1M) daemon and the automount(1M) com-
mand.
The autofs file format is ASCII; comment lines begin with the crosshatch (#) character. Parameters consist of a keyword followed by an
equal sign followed by the parameter value, of the form:
keyword=value
As shipped, the parameters in the autofs file are commented out. As root, you must uncomment a keyword-value line to make the value for
that parameter take effect.
Administrators can make changes to the startup parameters for automountd by logging in as root and editing the autofs file. Changes made to
autofs values on an automount or automountd command line override values in /etc/default/autofs. The /etc/default/autofs file is preserved
across operating system upgrades.
The following parameters are currently supported in the autofs file:
AUTOMOUNT_TIMEOUT=<num>
Specifies a duration, in seconds, that a file system is to remain mounted when not in use. The default value is 600 (10 minutes).
Equivalent to the -t option in automount.
AUTOMOUNT_VERBOSE=TRUE | FALSE
Verbose mode. Causes you to be notified of non-critical events, suchs as autofs mounts and unmounts. The default value is FALSE. Equiv-
alent to the -v option in automount.
AUTOMOUNTD_VERBOSE=TRUE | FALSE
Verbose mode. Causes status messages to be logged to /var/svc/log/system-filesystem-autofs:default.log. (See smf(5).) The default value
is FALSE. Equivalent to the -v option in automountd.
AUTOMOUNTD_NOBROWSE=<num>
Turn on or off browsing for all autofs mount points. The default value is FALSE. Equivalent to the -n option in automountd.
AUTOMOUNTD_TRACE=<num>
Expands each RPC call and logs it to /var/svc/log/system-filesystem-autofs:default.log. (See smf(5).) The default value, 0, turns off
such tracing. Starting with 1, with each higher value, the verbosity of trace output increases.
AUTOMOUNTD_ENV=<name>=<value>
Environment variables. Each environment variable-value pairing must be on its own line. You can specify multiple such pairings. There
are no environment variable settings supplied. For example: AUTOMOUNTD_ENV=DAY=TUES
SEE ALSO
automount(1M), automountd(1M), smf(5)
SunOS 5.11 2 Aug 2005 autofs(4)