Do you trust your users to follow your instructions? Post: 302940916

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

04-10-2015

Registered User

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.

edfair

View Public Profile for edfair

Find all posts by edfair

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. 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...

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!

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...

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.

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...

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.

LEARN ABOUT NETBSD

mlxctl

MLXCTL(8)						    BSD System Manager's Manual 						 MLXCTL(8)

NAME

     mlxctl -- Mylex DAC960 family management utility

SYNOPSIS

     mlxctl [-f dev] [-v] [-a] status [drive] [...]
     mlxctl [-f dev] [-a] detach [drive] [...]
     mlxctl [-f dev] [-a] check [drive] [...]
     mlxctl [-f dev] rebuild channel:target
     mlxctl [-f dev] cstatus
     mlxctl [-f dev] rescan
     mlxctl [-f dev] config

DESCRIPTION

     The mlxctl utility performs status monitoring and management functions for Mylex DAC960 RAID controllers and attached devices.

     The following options are available:

     -a       Apply the action to all drives attached to the controller.

     -f dev   Specify the control device to use.  The default is /dev/mlx0.

     -v       Increased verbosity.

     The following commands are available:

     cstatus  Display the controller's current status.

     status   Display the status of the specified drives.  This command returns 0 if all drives tested are online, 1 if one or more drives are
	      critical and 2 if one or more are offline.

     rescan   Re-scan the logical drive table, and attach or detach devices from the system as necessary.

     detach   Detach the specified drives.  Drives must be unmounted and unopened for this command to succeed.

     check    Initiate a consistency check and repair pass on a drive that provides redundancy (e.g., RAID1 or RAID5).	This command returns imme-
	      diately.	The status command can be used to monitor the progress of the check.

     rebuild  Rebuild onto the specified physical drive.  Note that there can be only one running rebuild operation per controller at any given
	      time.  This command returns immediately.	The cstatus command can be used to monitor the progress of the rebuild.

     config   Write the current system drive configuration to stdout.

EXAMPLES

     Display the status of drive ld3 attached to the controller mlx1:

	   mlxctl -f /dev/mlx1 -v status ld3

SEE ALSO

     ld(4), mlx(4)

HISTORY

     The mlxctl command first appeared in NetBSD 1.5.3, and was based on the mlxcontrol utility found in FreeBSD.

BUGS

     Modifying drive configuration is not yet supported.

     Some commands do not work with older firmware revisions.

     Error log extraction is not yet supported.

BSD
								  April 10, 2000							       BSD