Sponsored Content
Full Discussion: Why not automatic bootup
Top Forums UNIX for Dummies Questions & Answers Why not automatic bootup Post 62862 by asif iqbal on Monday 21st of February 2005 04:45:26 AM
Old 02-21-2005
How di I crosscheck it? Can you explain in detail?
thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Triple bootup

Hi guys, May I know how to install Solaris 8 in the way that I can triple boot it with my the other two OS: WIndows ME and Windows 2000 Pro. Can you all please kindly advise me on how to setup the triple boot process inorder to allow Windows ME to be the default OS when being ask to choose... (1 Reply)
Discussion started by: cia
1 Replies

2. UNIX for Advanced & Expert Users

bootup script

Hello there I need to run a script whenever i reboot or startup my HP-UX server. This script adds some routes to the route table, and it start third party aplications like "Star Manager". I thought i could do this simply putting the script in "/sbin/init.d, and a link to the script in... (7 Replies)
Discussion started by: vascobrito
7 Replies

3. UNIX for Dummies Questions & Answers

Bootup Error

Hi all The following error was displayed when a sco server (5.0.5) was booted. What should be done to overcome the problem. Replies appreciated. Bios 03.0 0130688 KB memory good 01 processor(s) in system remote console dialing on, please wait connect fail : modem off cpu clock... (6 Replies)
Discussion started by: raguramtgr
6 Replies

4. AIX

How to start ssh at bootup

Hi i installed ssh of version v 1.21 and my AIX is of 5.3. I want to start my ssh deamon at the startup can any one please help me out reg.. Thanks in advance.. (1 Reply)
Discussion started by: kmalla
1 Replies

5. SCO

Starting processes automatically on bootup

Hello - We have setup printers to startup in the /etc/rc.d/8 directory and when the SCO system is booted this script should kick them off or start them up but it doesn't. So I have to start it from root and leave the window open. I know this isn't right and trying to figure out what's missing. ... (13 Replies)
Discussion started by: dbm7230
13 Replies

6. UNIX for Advanced & Expert Users

system slows after bootup for some time

Hi, I am using a Linux system running at run level 3. I am finding a wired problem, once the system boots, the system terminal slows down, I need to type the characters repeatedly to enter my login and password info. Also running any commands takes time, it stays in this condition for some... (1 Reply)
Discussion started by: cjjoy
1 Replies

7. UNIX for Dummies Questions & Answers

bootup sequence

What is the boot up sequence in UNIX? (2 Replies)
Discussion started by: karthi_g
2 Replies

8. Red Hat

Stdin during rhel 7 bootup (systemd)

Hi All, I had a startup script (rc3.d/S01getinput) which will accept user inputs during the boot up in console. Basically it will prompt for input. It was working fine in RHEL6. Now I have migrated to RHEL 7 and script gets executed as part of the boot up process. But it does not... (1 Reply)
Discussion started by: kalpeer
1 Replies

9. AIX

Automatic Server bootup after power outage?

Hi everyone, We had a power outage few days ago, and I got the servers up and running but I was informed to look into, if there is a way to bring up the servers automatically/defaultly. I was told the windows admin has their server set up where the servers are up automatically if there is a... (11 Replies)
Discussion started by: Adnans2k
11 Replies

10. SCO

Error F painit on bootup

I have a known good external SCSI HD running SCO UNIX OpenServer 5.0.7. I decided that I wanted to be able to run this drive on another computer, so I bought the same SCSI card as before (LSI) and then attempted to boot on the other system. The bootup process hung with the error F painit. I've... (13 Replies)
Discussion started by: Transpower
13 Replies
explain_rename(3)					     Library Functions Manual						 explain_rename(3)

NAME
explain_rename - explain rename(2) errors SYNOPSIS
#include <libexplain/rename.h> const char *explain_rename(const char *oldpath, const char *newpath); const char *explain_errno_rename(int errnum, const char *oldpath, const char *newpath); void explain_message_rename(char *message, int message_size, const char *oldpath, const char *newpath); void explain_message_errno_rename(char *message, int message_size, int errnum, const char *oldpath, const char *newpath); DESCRIPTION
The functions declared in the <libexplain/rename.h> include file may be used to explain errors returned by the rename(2) system call. explain_rename const char *explain_rename(const char *oldpath, const char *newpath); The explain_rename function is used to obtain an explanation of an error returned by the rename(2) function. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (rename(oldpath, rewpath) < 0) { fprintf(stderr, "%s ", explain_rename(oldpath, newpath)); exit(EXIT_FAILURE); } oldpath The original oldpath, exactly as passed to the rename(2) system call. newpath The original newpath, exactly as passed to the rename(2) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_rename const char *explain_errno_rename(int errnum, const char *oldpath, const char *newpath); The explain_errno_rename function is used to obtain an explanation of an error returned by the rename(2) function. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (rename(oldpath, newpath) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_rename(err, oldpath, newpath)); exit(EXIT_FAILURE); } errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. oldpath The original oldpath, exactly as passed to the rename(2) system call. newpath The original newpath, exactly as passed to the rename(2) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_rename void explain_message_rename(char *message, int message_size, const char *oldpath, const char *newpath); The explain_message_rename function is used to obtain an explanation of an error returned by the rename(2) function. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (rename(oldpath, newpath) < 0) { char message[3000]; explain_message_rename(message, sizeof(message), oldpath, newpath); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. Because a message return buffer has been supplied, this function is thread safe, if the buffer is thread safe. message_size The size in bytes of the location in which to store the returned message. oldpath The original oldpath, exactly as passed to the rename(2) system call. newpath The original newpath, exactly as passed to the rename(2) system call. explain_message_errno_rename void explain_message_errno_rename(char *message, int message_size, int errnum, const char *oldpath, const char *newpath); The explain_message_errno_rename function is used to obtain an explanation of an error returned by the rename(2) function. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (rename(oldpath, newpath) < 0) { int err = errno; char message[3000]; explain_message_errno_rename(message, sizeof(message), err, oldpath, newpath); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. Because a message return buffer has been supplied, this function is thread safe, given a thread safe buffer. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. oldpath The original oldpath, exactly as passed to the rename(2) system call. newpath The original newpath, exactly as passed to the rename(2) system call. COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller AUTHOR
Written by Peter Miller <pmiller@opensource.org.au> explain_rename(3)
All times are GMT -4. The time now is 06:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy