/dev/null should not be a regular file. Look at
output on your working server. Then remove /dev/null on this server and use mknod to recreate /dev/null as a character special file with the same major and minor device numbers as /dev/null on your working server. (The rm and mknod will need to be done with appropriate privileges.)
PS The file mode is also wrong. /dev/null should be mode 666 not 644.
Last edited by Don Cragun; 10-26-2013 at 12:18 AM..
Reason: Add note on permissions.
This User Gave Thanks to Don Cragun For This Post:
I'm a newbie to the Unix world Help!
I have to maintain a host of Sybase database servers sitting on Unix Sun Solaris 8...I've been tasked with finding/creating a way to auto start/stop Unix via unix commands, specifically when the Unix servers need to be restarted we want Sybase to start... (2 Replies)
Hi...all
database - 10g Rs 2 with ASM
platform - Sun Solaris V890 64bit
This is the step i use to auto start the database n ASM: (auto start can start but need to kill lsvcrun first)
1 dbora---script
2 start_shutdown_asm.ksh---script
3. Dbora file must be put under /etc/init.d directory... (0 Replies)
i have two separate scripts that work nicely to curl and generate two files.. one html and one txt so a total of four.
When the script starts up i want it to:
call and run shellscripta
call and run shellscriptb
sleep for about 40 seconds
again run shellscripta
again run shellscriptb
check... (4 Replies)
Hi All,
I would like to develop a shell script for stop & start an application server (1-4) on Solaris box. Here are the user requirements for this task.
1. User will input the option which server they wish to stop.
2. Will clear cache files from specific location.
3. ... (1 Reply)
Hello All,
I am completely new to shell scripting. I had to write a script that starts and stop the queue manager in Websphere MQ. We are on Linux 64-bit patform.
The script should stop the queue manager and all the processes related to websphere MQ. It should be a clean stop. Once the queue... (3 Replies)
Hi,
I need to create a shell script for automated server patching, with the following scenario:
I have two Linux servers Primary and secondary.
Server patching should start on Primary 1st and then secondary.
1st check both servers are up and running.
Then stop primary and patching will... (1 Reply)
Discussion started by: rcroyal88
1 Replies
LEARN ABOUT LINUX
hd
HD(4) Linux Programmer's Manual HD(4)NAME
hd - MFM/IDE hard disk devices
DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major
device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave
hdd.
General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order
the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the
four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi-
cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions
on an IDE disk.
For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the
second one.
They are typically created by:
mknod -m 660 /dev/hda b 3 0
mknod -m 660 /dev/hda1 b 3 1
mknod -m 660 /dev/hda2 b 3 2
...
mknod -m 660 /dev/hda8 b 3 8
mknod -m 660 /dev/hdb b 3 64
mknod -m 660 /dev/hdb1 b 3 65
mknod -m 660 /dev/hdb2 b 3 66
...
mknod -m 660 /dev/hdb8 b 3 72
chown root:disk /dev/hd*
FILES
/dev/hd*
SEE ALSO chown(1), mknod(1), sd(4), mount(8)COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 HD(4)