08-12-2015
Many users (or customers) can't even follow instructions written in a support contract; like "if something breaks call us". They pay you for support but then, when something stops working they do their own thing.
"The package started misbehaving so we uninstalled it, reinstalled it, edited its config files, but then it started doing something else, very strange. Then we noticed that we couldn't print or send email."
So they originally had one problem, have really messed with it, and now created a further 60 issues. Now that they've really screwed it they call you and declare that they have a support contract which they wish to invoke. Please get it all back working again (for no extra fee). They also cannot tell you everything they did and/or may even deny that they've done anything since it broke.
Sound familiar? Particularly happens in family run businesses where a family member feels entitled to mess with the system. After all, it's our server, you only support it!!!
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
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
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
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
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
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?
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
LEARN ABOUT DEBIAN
which-pkg-broke
which-pkg-broke(1) debian-goodies which-pkg-broke(1)
NAME
which-pkg-broke - find which package might have broken another
SYNOPSIS
which-pkg-broke package
DESCRIPTION
The which-pkg-broke program will retrieve a list of the named package and all its dependencies sorted by the time they were installed on
the system (as determined from the mtime information of /var/lib/dpkg/info/*.list .
This tool makes it possible for a system admin to obtain information that might correlate installation of package dependencies with a pack-
age breakage in order to find which package update might be responsible for the breakage.
EXAMPLES
This tool can be useful determine which package dependencies were upgraded more recently and might be associated with the bug that is being
observed. For example, if aptitude stops working properly, an administrator can run:
$ which-pkg-broke aptitude
Package <libapt-pkg-libc6.3-5-3.3> has no install time info
libdb1-compat Fri Aug 8 03:02:11 2003
libsigc++-1.2-5c102 Fri Aug 8 05:15:58 2003
aptitude Sun Jan 11 17:38:06 2004
libncurses5 Sun Jan 18 08:11:05 2004
libc6 Thu Jan 22 07:55:10 2004
libgcc1 Tue Jan 27 07:37:22 2004
gcc-3.3-base Tue Jan 27 07:37:31 2004
libstdc++5 Tue Jan 27 07:37:32 2004
So depending on exactly when the misbehaviour started, there may be a reason to point the finger at a more-recently updated library like
libstdc++ or libncurses, which are more-recently installed than aptitude itself.
SEE ALSO
rc-alert(1)
AUTHOR
which-pkg-broke was written by Bill Gribble <grib AT billgribble.com>
This manual page was written by Javier Fernandez-Sanguino for the Debian GNU/Linux distribution.
debian-goodies July 24 2006 which-pkg-broke(1)