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 CENTOS
papi_ipc
PAPI_ipc(3) PAPI PAPI_ipc(3)
NAME
PAPI_ipc -
Simplified call to get instructions per cycle, real and processor time.
SYNOPSIS
Detailed Description
C Interface:
#include <papi.h>
int PAPI_ipc( float *rtime, float *ptime, long long *ins, float *ipc );
Parameters:
*rtime total realtime since the first call
*ptime total process time since the first call
*ins total instructions since the first call
*ipc incremental instructions per cycle since the last call
Return values:
PAPI_EINVAL The counters were already started by something other than PAPI_ipc().
PAPI_ENOEVNT The floating point operations event does not exist.
PAPI_ENOMEM Insufficient memory to complete the operation.
The first call to PAPI_ipc() will initialize the PAPI High Level interface, set up the counters to monitor PAPI_TOT_INS and PAPI_TOT_CYC
events and start the counters.
Subsequent calls will read the counters and return total real time, total process time, total instructions since the start of the
measurement and the IPC rate since the latest call to PAPI_ipc().
A call to PAPI_stop_counters() will stop the counters from running and then calls such as PAPI_start_counters() or other rate calls can
safely be used.
PAPI_ipc should return a ratio greater than 1.0, indicating instruction level parallelism within the chip. The larger this ratio the more
effeciently the program is running.
See Also:
PAPI_flips()
PAPI_flops()
PAPI_epc()
PAPI_stop_counters()
Author
Generated automatically by Doxygen for PAPI from the source code.
Version 5.2.0.0 Tue Jun 17 2014 PAPI_ipc(3)