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 MOJAVE

auditd

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

NAME

     auditd -- audit log management daemon

SYNOPSIS

     auditd [-d | -l]

DESCRIPTION

     The auditd daemon responds to requests from the audit(8) utility and notifications from the kernel.  It manages the resulting audit log files
     and specified log file locations.

     The options are as follows:

     -d      Starts the daemon in debug mode -- it will not daemonize.

     -l      This option is for when auditd is configured to start on-demand using launchd(8).

     Optionally, the audit review group "audit" may be created.  Non-privileged users that are members of this group may read the audit trail log
     files.

NOTE

     To assure uninterrupted audit support, the auditd daemon should not be started and stopped manually.  Instead, the audit(8) command should be
     used to inform the daemon to change state/configuration after altering the audit_control file.

     If auditd is started on-demand by launchd(8) then auditing should only be started and stopped with audit(8).

     On Mac OS X, auditd uses the asl(3) API for writing system log messages.  Therefore, only the audit administrator and members of the audit
     review group will be able to read the system log entries.

FILES

     /var/audit     Default directory for storing audit log files.

     /etc/security  The directory containing the auditing configuration files audit_class(5), audit_control(5), audit_event(5), and audit_warn(5).

COMPATIBILITY

     The historical -h and -s flags are now configured using audit_control(5) policy flags ahlt and cnt, and are no longer available as arguments
     to auditd.

SEE ALSO

     asl(3), libauditd(3), audit(4), audit_class(5), audit_control(5), audit_event(5), audit_warn(5), audit(8), launchd(8)

HISTORY

     The OpenBSM implementation was created by McAfee Research, the security division of McAfee Inc., under contract to Apple Computer Inc. in
     2004.  It was subsequently adopted by the TrustedBSD Project as the foundation for the OpenBSM distribution.

AUTHORS

     This software was created by McAfee Research, the security research division of McAfee, Inc., under contract to Apple Computer Inc.  Addi-
     tional authors include Wayne Salamon, Robert Watson, and SPARTA Inc.

     The Basic Security Module (BSM) interface to audit records and audit event stream format were defined by Sun Microsystems.

BSD
								 December 11, 2008							       BSD