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 REDHAT
msgattrib
MSGATTRIB(1) GNU MSGATTRIB(1)
NAME
msgattrib - attribute matching and manipulation on message catalog
SYNOPSIS
msgattrib [OPTION] [INPUTFILE]
DESCRIPTION
Filters the messages of a translation catalog according to their attributes, and manipulates the attributes.
Mandatory arguments to long options are mandatory for short options too.
Input file location:
INPUTFILE
input PO file
-D, --directory=DIRECTORY
add DIRECTORY to list for input files search
If no input file is given or if it is -, standard input is read.
Output file location:
-o, --output-file=FILE
write output to specified file
The results are written to standard output if no output file is specified or if it is -.
Message selection:
--translated
keep translated, remove untranslated messages
--untranslated
keep untranslated, remove translated messages
--no-fuzzy
remove 'fuzzy' marked messages
--only-fuzzy
keep 'fuzzy' marked messages
--no-obsolete
remove obsolete #~ messages
--only-obsolete
keep obsolete #~ messages
Attribute manipulation:
--set-fuzzy
set all messages 'fuzzy'
--clear-fuzzy
set all messages non-'fuzzy'
--set-obsolete
set all messages obsolete
--clear-obsolete
set all messages non-obsolete
--fuzzy
synonym for --only-fuzzy --clear-fuzzy
--obsolete
synonym for --only-obsolete --clear-obsolete
Output details:
-e, --no-escape
do not use C escapes in output (default)
-E, --escape
use C escapes in output, no extended chars
--force-po
write PO file even if empty
-i, --indent
write the .po file using indented style
--no-location
do not write '#: filename:line' lines
-n, --add-location
generate '#: filename:line' lines (default)
--strict
write out strict Uniforum conforming .po file
-w, --width=NUMBER
set output page width
--no-wrap
do not break long message lines, longer than the output page width, into several lines
-s, --sort-output
generate sorted output
-F, --sort-by-file
sort output by file location
Informative output:
-h, --help
display this help and exit
-V, --version
output version information and exit
AUTHOR
Written by Bruno Haible.
REPORTING BUGS
Report bugs to <bug-gnu-gettext@gnu.org>.
COPYRIGHT
Copyright (C) 2001-2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
The full documentation for msgattrib is maintained as a Texinfo manual. If the info and msgattrib programs are properly installed at your
site, the command
info msgattrib
should give you access to the complete manual.
GNU gettext 0.11.4 July 2002 MSGATTRIB(1)