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
UBT(4) BSD Kernel Interfaces Manual UBT(4)
NAME
ubt -- USB Bluetooth driver
SYNOPSIS
ubt* at uhub? port ? configuration ? interface ?
DESCRIPTION
The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack.
USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims. The second interface is used for Isochronous data and
will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable.
The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current
configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables.
By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent.
Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption. The fol-
lowing extract may be useful as a general guidance though details may differ between manufacturers.
0 No active voice channels
1 One voice channel with 8-bit encoding
2 Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding.
3 Three voice channels with 8-bit encoding
4 Two voice channels with 16-bit encoding
5 Three voice channels with 16-bit encoding
SEE ALSO
bluetooth(4), uhub(4), sysctl(8)
HISTORY
This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson. It was rewritten to support socket
based Bluetooth access for NetBSD 4.0 by Iain Hibbert.
CAVEATS
Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO
packet size that the stack will use. This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3
bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize'
sysctl variable.
For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17
bytes. This gives possible values of:
(17 * 1) - 3 = 14
(17 * 2) - 3 = 31
(17 * 3) - 3 = 48
(17 * 4) - 3 = 65
(17 * 5) - 3 = 82
etc.
btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header
bytes.
The SCO packet size can be changed using the 'scomtu' option to btconfig(8).
The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem.
BUGS
The Isochronous configuration can only be changed when the device is not marked up.
BSD
August 27, 2006 BSD