Hello!
During the last couple of days I've ran into some strange behavior on DU
v4.0B
1.
A disk used on an Ultrix-machine was to be set up as a second swap and
an AdvFS-domain. I wanted to make my own partition table and ran
"disklabel -e" after having set "EDITOR=vi; export EDITOR".
Everything seemed OK, but the new label never got into effect.
Then I found all disklabels in the /tmp-area:
barney /# ls -l /tmp
total 28
drwxrwxrwt 2 root daemon 8192 Mar 6 10:06 .X11-unix
-rw------- 1 root system 1003 Mar 24 14:04 EdDk.aaaatra
-rw------- 1 root system 990 Mar 24 14:21 EdDk.aaaavCa
-rw------- 1 root system 990 Mar 24 14:47 EdDk.aaabdra
-rw------- 1 root system 991 Mar 24 15:10 EdDk.aaabfma
-rw------- 1 root system 993 Mar 24 15:16 EdDk.aaabiza
-rw------- 1 root system 993 Mar 24 15:28 EdDk.aaabkBa
-rw------- 1 root system 991 Mar 24 15:24 EdDk.aaabkha
-rw------- 1 root system 999 Mar 24 15:32 EdDk.aaablBa
-rw------- 1 root system 996 Mar 24 15:38 EdDk.aaabmfa
barney /# uname -a
OSF1 barney V4.0 564 alpha
Here is the commands I wanted to set up the disk with:
# disklabel -e rz1 # also used /dev/rz1c
# disklabel -wr -t advfs rz1g
The disklabel last edited:
barney /# more /tmp/EdDk.aaabmfa
# /dev/rrz1a:
type: SCSI
disk: ST12550N
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 81
tracks/cylinder: 19
sectors/cylinder: 1539
cylinders: 2708
sectors/unit: 4178874
rpm: 7200
interleave: 1
trackskew: 7
cylinderskew: 16
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 unused 0 0 # (Cyl. 0 -85*)
b: 262144 131072 unused 0 0 # (Cyl. 85*-255*)
c: 4178874 0 unused 0 0 # (Cyl. 0 -2715*)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 3785656 393216 unused 0 0 # (Cyl. 255*-1485*)
h: 0 0 unused 0 0 # (Cyl. 0 - -1)
2.
The batch command. According to "man batch":
SYNOPSIS
batch
... The batch command runs jobs when the system load level permits.
I've not been able to find what parameter who's important.
Is it something in the kernel or is it just run run when the load is < 1?
Thanks in advance!
Kjell Andresen Systems administrator, University of Oslo, Norway
Center for Information Technology Services and
Department of Geophysics
Received on Thu Mar 26 1998 - 08:36:15 NZST