Sponsored Content
The Lounge War Stories Do you trust your users to follow your instructions? Post 302940916 by edfair on Friday 10th of April 2015 12:25:37 AM
Old 04-10-2015
Do you trust your users to follow your instructions?

This happened a long time ago and some of the details may not be exact. Customer had obsolete hardware running an obsolete SCO OS and some type of database program with data scattered around the system. There were 2-1g SCSI drives, both split in half, with the 3 filesystems automatically loading on boot.

The non boot hard drive upchucked and went out to data recovery while I replaced the hard drive, partioned it, and created the filesystems awaiting Monday morning and left with instructions to not attempt a restore of the data if it came in.

When I got there on Monday the data had been restored. You can imagine that their data was totally corrupted. Some parts were good, some parts were bad, and they had no understanding of how it happened. Restoring to a system without the attached filesystem dropped the stuff to the assumed proper place on the root drive but only those files that would fit. And as the drive filled up less and less would fit.

The person who did the restore told me that the owner of the company had told him to restore it in spite of my instructions not to.

It ended up in the court system, my side to get reimbursed for some time and parts, his counter suit for $40,000 for the work to recover his data, later reduced to $25,000 so it would stay in small claims court. The second judge to hear it suggested that we kiss and make up since it was going to cost both of us more to proceed than we would win.

I understood what had happened, had insisted on backups that would have allowed full recovery, but wasn't interested in dealing with them any more.
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ssh2-keygen trust issue

I have two systems SysA & SysB having the same userid sharing the home directory via NFS mount. I need to know the steps to setup ssh trust between these two systems given that both share the home dir. I have tried all the steps to generate the keys & then creating identification &... (2 Replies)
Discussion started by: deo_kaustubh
2 Replies

2. Solaris

configuring user as trust

Hi Gurus, Got another issue. I am trying to configure a user to run some scripts through trusted user where in while logging to remote system it shouldn't ask for password. i did following to get it working but its not working i create a private and public key with the below... (1 Reply)
Discussion started by: kumarmani
1 Replies

3. HP-UX

Not Trust Host 10.10.10.10

I get a message similar to this, in the syslog file. Actually, I am trying to let the host at 10.10.10.10 access the HP-UX system. How do I get it trusted? Thanks! (2 Replies)
Discussion started by: instant000
2 Replies

4. UNIX for Dummies Questions & Answers

ssh trust issue

Hi, i am setting up ssh trust setup between two servers where SVRA is a solaris box and SVRB is a Red Hat Linux. It is asking for the password all the time. I have copied over the SVRA:/home/nagios/.ssh/id_dsa.pub as authorized_keys on to SVRB:/dat01/home/nagios/.ssh/ -bash-3.00$ ssh -vvv... (4 Replies)
Discussion started by: uxadmin007
4 Replies

5. Linux

SCEP and Trust Anchor

Hi Does anybody knows about the simple certificate enrollment protocol details ? if yes please provide me the details. And what is a trust anchor profile ? Thanks in advance. (0 Replies)
Discussion started by: chaitus.28
0 Replies

6. Shell Programming and Scripting

SSH Trust Testing

Hi, I want test the ssh trust between two host. It works fine if the trust is working fine but if the trust is not working fine it gets stuck. #!/bin/sh >/users/test/ssh.txt for i in `cat /users/test/host.txt`; do ssh test@$i uname -a >> /users/test/ssh.txt test=`cat... (0 Replies)
Discussion started by: Abhayman
0 Replies

7. What is on Your Mind?

Twitter Users: Follow the Forums on Twitter

Hey Twitter Users, You can follow the forums on Twitter: https://twitter.com/unixlinux @unixlinux Current Twitter Stats: TWEETS 76.4K FOLLOWERS 54.3K Comments or questions? Please post below. (1 Reply)
Discussion started by: Neo
1 Replies
SD(4)							     Linux Programmer's Manual							     SD(4)

NAME
sd - driver for SCSI disk drives SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */ #include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */ CONFIGURATION
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti- tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive. SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num- ber is the number of the physical drive in order of detection, and partition_number is as follows: partition 0 is the whole drive partitions 1-4 are the DOS "primary" partitions partitions 5-8 are the DOS "extended" (or "logical") partitions For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system. At this time, only block devices are provided. Raw devices have not yet been implemented. DESCRIPTION
The following ioctls are provided: HDIO_GETGEO Returns the BIOS disk parameters in the following structure: struct hd_geometry { unsigned char heads; unsigned char sectors; unsigned short cylinders; unsigned long start; }; A pointer to this structure is passed as the ioctl(2) parameter. The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters. BLKGETSIZE Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long. BLKRRPART Forces a reread of the SCSI disk partition tables. No parameter is needed. The SCSI ioctl(2) operations are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl(2) will fail with the error EINVAL. FILES
/dev/sd[a-h]: the whole device /dev/sd[a-h][0-8]: individual block partitions COLOPHON
This page is part of release 3.44 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 2012-05-03 SD(4)
All times are GMT -4. The time now is 10:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy