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

Sponsored Content

The Lounge War Stories Do you trust your users to follow your instructions? Post 302951978 by hicksd8 on Wednesday 12th of August 2015 10:35:07 AM

08-12-2015

Moderator

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

hicksd8

View Public Profile for hicksd8

Find all posts by hicksd8

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 CENTOS

sgetmask

SGETMASK(2)						     Linux Programmer's Manual						       SGETMASK(2)

NAME

       sgetmask, ssetmask - manipulation of signal mask (obsolete)

SYNOPSIS

       long sgetmask(void);

       long ssetmask(long newmask);

       Note: There are no glibc wrappers for these system calls; see NOTES.

DESCRIPTION

       These system calls are obsolete.  Do not use them; use sigprocmask(2) instead.

       sgetmask() returns the signal mask of the calling process.

       ssetmask() sets the signal mask of the calling process to the value given in newmask.  The previous signal mask is returned.

       The  signal  masks dealt with by these two system calls are plain bit masks (unlike the sigset_t used by sigprocmask(2)); use sigmask(3) to
       create and inspect these masks.

RETURN VALUE

       sgetmask() always successfully returns the signal mask.	ssetmask() always succeeds, and returns the previous signal mask.

ERRORS

       These system calls always succeed.

CONFORMING TO

       These system calls are Linux-specific.

NOTES

       Glibc does not provide wrappers for these obsolete system calls; in the unlikely event that you want to call them, use syscall(2).

       These system calls are unaware of signal numbers greater than 31 (i.e., real-time signals).

       It is not possible to block SIGSTOP or SIGKILL.

SEE ALSO

       sigprocmask(2), signal(7)

COLOPHON

       This page is part of release 3.53 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-07-13							       SGETMASK(2)