08-19-2001
Re-initializing startup files without rebooting
Sorry for the newbie question. I'm using OSX BSD by remotely logging in and need to re-initialize the startup sequence but don't want to reboot the machine. How can I do it?
Thanks for any help.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
log files for startup for AIX is /etc/rc.log.old
how about for hpux and solaris? (1 Reply)
Discussion started by: yls177
1 Replies
2. AIX
Hi Every Body, I want to know which files are read by the system during startup (initialization files) & in which order they are read? (2 Replies)
Discussion started by: aldowsary
2 Replies
3. SuSE
Hi Everybody
I am totally new to Linux.
We are using Suse Linux version 9.
Currently we have 4 to 5 shell scripts which needs to be executed manually by the users.I want these scripts to be run automatically when system starts...something like system startup service.
When system is... (1 Reply)
Discussion started by: appleforme1415
1 Replies
4. UNIX for Dummies Questions & Answers
hello,
i want to know how to initialize a file to an empty one in korn shell scripting? i'm using a file name and building it during a while loop using >>. The problem occurs when the file is not empty before reaching the while loop. therefore, i want to initialize it before the loop to get... (6 Replies)
Discussion started by: alrinno
6 Replies
5. Shell Programming and Scripting
hi everyone...
we have to run any python file e.g. show.py at startup..i.e. when OS starts it runs automatically.
we are proceeding this way,
writing a startup script named forfyp2 ,pasting it in init.d , making it exe using chmod , creating startup links using update-rc.d forfyp2 defaults.... (1 Reply)
Discussion started by: sarosh
1 Replies
6. UNIX for Dummies Questions & Answers
I was going through a server hardening manual.
At some interval it was mentioned that there should not be any alias for commands defined in roots startup files .
How would i check it? (3 Replies)
Discussion started by: pinga123
3 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
Can some one pls explain the order in which the startup files are run?
For Bourne shell .profile is run., But what other startup files are present?
When is the .aliases file called. (4 Replies)
Discussion started by: gsrikanth99
4 Replies
8. Shell Programming and Scripting
Hi, I am running a script which produces a number of intermediate output files for each time step. is there a way to remove these intermediate files and just retain the final output at every end of the loop, like sort of an initialization process? this the inefficient way i do it.
for i in... (3 Replies)
Discussion started by: ida1215
3 Replies
9. Shell Programming and Scripting
I copied the script from an AskUbuntu post -
#!/bin/bash
### BEGIN INIT INFO
# Provides: tomcat7
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/Stop Tomcat server
### END INIT INFO
... (14 Replies)
Discussion started by: Hijanoqu
14 Replies
LEARN ABOUT OSF1
vollogcnvt
vollogcnvt(8) System Manager's Manual vollogcnvt(8)
NAME
vollogcnvt - Logical Storage Manager BCL-to-DRL logging conversion utility
SYNOPSIS
/usr/sbin/vollogcnvt [-g diskgroup]
OPTIONS
Limits the conversion of logging subdisks to volumes in the specified disk group.
DESCRIPTION
The vollogcnvt script is a migration tool for Logical Storage Manager (LSM) administrators who are currently using the block-change logging
(BCL) feature. Beginning with the Version 5.0 release of Tru64 UNIX, the BCL feature of LSM is being replaced with the dirty-region logging
(DRL) feature.
The vollogcnvt script attempts to convert volumes with BCL enabled to volumes with DRL enabled. If called without specifying a disk group,
vollogcnvt attempts the BCL-to-DRL conversion for all volumes across all disk groups.
If logging cannot be re-enabled in the DRL scheme, a warning is sent to the console.
For volumes whose BCL subdisks will not work in the DRL scheme, logging is disabled.
Log subdisks that cannot be converted to DRL will be disassociated from its volume only if at least one of the log subdisks for that volume
could be converted. Otherwise, the configuration will not change and logging will be disabled. Those volumes that could not be converted,
for example all of its log subdisks are too small, will have logging disabled.
At system startup, the vollogcnvt script runs automatically and logs such errors to binlog and sends mail to root. This happens at each
reboot until the DRL is manually converted or when logging is disabled. If the script runs at startup or manually, warnings are sent to
the console.
For details and guidelines on using DRL, refer to the Logical Storage Manager guide.
SEE ALSO
binlogd(8), dia(8), volintro(8)
vollogcnvt(8)