Defining variables at boot time


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Defining variables at boot time
# 8  
Old 01-07-2002
This should work for both sh and ksh. If you are using csh, then it needs to be in /etc/.login
thehoghunter
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Boot time driver conflict

I have a Microdia web cam. Some times it won't work if and only if there is a "HV7131R image sensor detected" statement in the boot up. In this case when I try to get a .png snapshot all I get is a frame full of what appears to be white noise only it is mostly green. Here is the command I am... (0 Replies)
Discussion started by: slak0
0 Replies

2. Shell Programming and Scripting

Defining Dynamic Number of Variables in a Bash Script

Code: $ cat test.bash #!/bin/bash job=$1 steps=$2 num=$(echo "$@" | wc -w) Example Submission: $ ./test.bash BS01 3 1 2 3 What: (2 Replies)
Discussion started by: mkastin
2 Replies

3. Ubuntu

Upgrading 9.04 version 9.10 - slow boot time

After upgrading my 9.04 version to the 9.10 my boot time duplicates. I donīt know the reason why the time of boot gets to the double. Someone ??? Thx. (1 Reply)
Discussion started by: diesan
1 Replies

4. HP-UX

I want to get machine boot up time

I use the uptime command,but it only show how long system has been up up 18 days but I want the this format machine boot time YYYY-MM-DD hh:mm:ss does any command can get that or how to i use program to do this (6 Replies)
Discussion started by: alert0919
6 Replies

5. HP-UX

HP UX start process at boot time

When I get start program at boot I read which run level /sbin/rcx.d runlevel=0.....x only read directory which directory name has UpperCase 'S' is not enough someone says that I need to reference another file which file I need to reference 1)/etc/rc.config.d/all file which parameter... (4 Replies)
Discussion started by: alert0919
4 Replies

6. Shell Programming and Scripting

defining variables

Hey all, I was wondering if someone would take a look at this script I'm working on. I don't know if i have the syntax correct for my variables and if the for loop is written correctly. any assistance would be greatly appreciated. #!/usr/bin/bash ###########################################... (12 Replies)
Discussion started by: em23
12 Replies

7. Programming

How to get time since last boot?

How do I get the number of tics or seconds since the last boot? How do I convert tics to seconds? Thanks, Siegfried (3 Replies)
Discussion started by: siegfried
3 Replies

8. UNIX for Dummies Questions & Answers

Defining Variables

I'm trying to define a variable named sin I already have a variable named cos, which has the value "hello" I want sin to have the value of "hellothere", so sin would be something like sin = $cos & "there" but I'm not sure that I know the syntax. Can anyone help? :confused: (4 Replies)
Discussion started by: sailorliones
4 Replies

9. BSD

Reduce boot-time delay on FreeBSD?

Say for instance, I would like to reduce the delay/waiting time for the boot-time menu from 10 seconds to 5 seconds, how would I go about doing it? From what I've been able to find, entering "autoboot 5" into the right file would take care of that for me, but the man pages are unclear as to... (1 Reply)
Discussion started by: DownSouthMoe
1 Replies

10. UNIX for Advanced & Expert Users

start a process at boot up time

Hi, I have a program that check the IP address and automatic update it to the DNS server. I would like to run this program when the computer bootup after pppd get a connection. How do I add it to the init file. Does any one have any information of how to do it. I run a Linux Mandrake as a... (1 Reply)
Discussion started by: vtran4270
1 Replies
Login or Register to Ask a Question
advfsd(8)						      System Manager's Manual							 advfsd(8)

NAME
advfsd - Starts the AdvFS graphical user interface (GUI) daemon SYNOPSIS
/usr/sbin/advfsd DESCRIPTION
The AdvFS daemon, advfsd, is a process required by the AdvFS GUI (dtadvfs). The advfsd daemon issues commands and obtains system information on behalf of the AdvFS GUI. The /usr/var/advfs/daemon/socket/hosts.allow file contains a list of all hosts on which the advfsd daemon will allow the AdvFS GUI to run. This file can be edited to add or remove hosts. Each host name must be on a separate line. For example: host1 host3 host27 The /usr/var/advfs/daemon/socket/gui.passwd file, if it exists, is used by advfsd to force a dtadvfs user to enter a unique password when attempting to connect to the host. The first line of this file is the unique password required by the GUI. For example: guipassword For security reasons, do not use the password of the root user or any other user; make up a unique name and do not encrypt it. The advfsd daemon allows Simple Network Management Protocol (SNMP) clients such as NetView or Performance Manager (PM) to request AdvFS file system information. SNMP clients cannot issue system configuration commands to the advfsd daemon. The advfsd daemon is automatically started at boot time. Under normal conditions, this daemon does not need to be run manually. If you do not want to have the daemon started at boot time, move the /sbin/rc3.d/s53advfsd file from its default location to another directory and run it from that directory. Whenever you want to run the daemon at boot time, move the s53advfsd file back to the /sbin/rc3.d directory. The daemon (called an agent in the dtadvfs GUI interface) employs a file, /usr/var/advfs/daemon/disks.ignore, in which you can place the names of disks that the daemon will ignore when it gathers information about disks on the system. If you use the disks.ignore file, you can improve the performance of the dtadvfs GUI. Each line in the disks.ignore file contains the name of a disk (with no directory partition letter) to be ignored by the daemon. For example, to cause the disks /dev/disk/dsk3d and /dev/disk/dsk2g to be ignored, enter the following names on separate lines in the file: dsk2 dsk3 You cannot ignore an LSM volume by including the LSM volume name in the disks.ignore file; you must list the disks from which the LSM vol- ume is built. To ignore a complete disk group, you must list all the disks in it. Because all partitions on the listed disks will be ignored, unexpected results may occur if a disk has partitions belonging to more than one disk group. The disks.ignore file is processed each time the disks are checked. This means that if a disk fails or becomes unavailable, you can add the disk name to the disks.ignore file and the daemon will ignore it. Once the disk is available, remove the entry from the file. There is no need to stop the daemon. For more information, see the GUI interface reference page , dtadvfs(8). RESTRICTIONS
Only one advfsd daemon can be running on a system at a given time. If a second advfsd daemon attempts to start, it will fail. You must be the root user to use this utility and you must register the Advanced File System Utilities license. FILES
The script that starts the advfsd daemon at boot time. The advfsd message catalog. The SNMP data files. The sh scripts used by the dae- mon to execute commands. The advfsd daemon executable. The advfsd daemon message log file. Remove or copy this log to another location periodically to prevent the log from becoming too large. The security file that lists all hosts with permission to connect to the advfsd daemon with the AdvFS GUI (dtadvfs). The advfsd password file. The file that lists all disks for the advfsd daemon to ignore when col- lecting statistics about resources. SEE ALSO
advfs(4), dtadvfs(8) advfsd(8)