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

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 Replies)
Discussion started by: deo_kaustubh
2 Replies

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... (1 Reply)
Discussion started by: kumarmani
1 Replies

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! (2 Replies)
Discussion started by: instant000
2 Replies

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... (4 Replies)
Discussion started by: uxadmin007
4 Replies

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. (0 Replies)
Discussion started by: chaitus.28
0 Replies

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... (0 Replies)
Discussion started by: Abhayman
0 Replies

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. (1 Reply)
Discussion started by: Neo
1 Replies
ctrun(1)							   User Commands							  ctrun(1)

NAME
ctrun - execute command in a process contract SYNOPSIS
/usr/bin/ctrun [options] command [ argument...] DESCRIPTION
The ctrun utility starts a command in a newly created process contract. ctrun holds the contract and can be instructed to output or respond to events that occur within the contract. For additional information about process contracts, see contract(4) and process(4). OPTIONS
The following options are supported: -i event,[event ...] -f event,[event ...] Sets the informative and fatal events, respectively. The following are valid events: core A member process dumped core. core events are informative by default. empty The last member of the process contract exited. exit A member process exited. fork A process was added to the process contract. hwerr A member process encountered a hardware error. hwerr events are fatal by default. signal A member process received a fatal signal from a process in a different process contract. Only core, hwerr, and signal events can be made fatal. More events can be delivered than requested if ctrun requires them for its own purposes. For example, empty messages are always requested if a lifetime of contract is specified. See -l. -l lifetime The following valid lifetime values are supported: child ctrun exits when the command exits, regardless of whether the contract is empty. contract ctrun exits only when the contract exits. This is the default. none ctrun exits immediately, orphaning the contract. -o option,[option ...] The following options are supported: noorphan Kills all processes in the contract if the holder (ctrun) exits. This option is invalid when a lifetime of none is specified. pgrponly If a fatal error occurs, kills at most the process group of which the errant process is a member. regent The contract inherits inheritable contracts when abandoned by member processes. -r count If the contract encounters a fault, this option attempts to restart the command count times. If count is 0, the attempt to restart con- tinues indefinitely. By default, ctrun does not attempt to restart the command. This option is invalid if a lifetime other than contract is specified or if the pgrponly option is used. -t If the contract created by ctrun inherited subcontracts from its member processes, attempts to transfer them to the new contract when restarting. This option is invalid unless -r is also specified. -v Displays contract events and ctrun actions as they occur. -V Displays verbose contract events, as are displayed by the -v option of ctwatch. Implies -v. OPERANDS
The following operands are supported: argument One of the strings treated as an argument to command. command The command to be passed to execvp(2). See exec(2). EXAMPLES
Example 1: Running a Shell in a New Process Contract The following example runs a shell in a new process contract: example% ctrun -l child -o pgrponly ksh The -l child option argument is specified so that ctrun won't wait until all children of the shell have exited. -o pgrponly is specified because an interactive ksh puts each job in a new process group, and an error in one job is unlikely to affect the others. Example 2: Running a Simple Server The following example runs a simple server: example% ctrun -r 0 -t -f hwerr,core,signal server The -r 0 and -t options are specified to indicate that if the server encounters a fatal error, ctrun should try to restart it. The -f option makes "hwerr", "core", and "signal" fatal events. EXIT STATUS
If command is specified and successfully invoked (see exec(2)), the exit status of ctrun is the exit status of command. Otherwise, ctrun exits with one of the following values: 123 The child process exited abnormally. 124 ctrun encountered an internal error. 125 Invalid arguments were provided to ctrun. 126 command was found but could not be invoked. 127 command could not be found. FILES
/system/contract/process/* ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ Human Readable Output is Unstable. Invocation is Evolving. SEE ALSO
ctstat(1), ctwatch(1), exec(2), contract(4), process(4), attributes(5) SunOS 5.10 15 Jul 2004 ctrun(1)
All times are GMT -4. The time now is 07:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy