12-07-2011
Hi bartus11,
No i am now connecting to the ip address starting with 148,using putty from my desktop(running on windos xp),,as per admin's mail,,,,the ip address starting with 148 is a taxi server which has remote access enabled,,,,,
does this ring any bell,,,,,,
5 More Discussions You Might Find Interesting
1. Solaris
Hello!
I have a Linux nfs server (called server100 below) with a export nfs. My problem is that the Solaris client (called client100 below) doesn't seems to like it. In the Solaris syslog I got following messages (and after a while the solaris client behave liked its hanged/to buzy). Also see... (3 Replies)
Discussion started by: sap4ever
3 Replies
2. Programming
I have a Perl script that worked fine before moving it to justhost.com. It was on a Windows/Apache server. Just host is using UNIX. Other Perl scripts on other sites that were also moved work fine so I know Perl is functioning.
The script is called cwrmail.pl and is located in my cgi-bin.
When I... (9 Replies)
Discussion started by: BigBobbyB
9 Replies
3. Shell Programming and Scripting
Dear Friends,
Sorry for this basic request. But I just started learning Ksh recently and still I am a newbie in this field.
Q: I have files on one server and the date format is 20121001000009_224625.in which has year (yyyy) month (mm) and date (dd). I have these files on server A. The task... (8 Replies)
Discussion started by: BrownBob
8 Replies
4. Shell Programming and Scripting
I need to connect to a ftp server-1 from linux server-2 and copy/get a file from server-1 which follows a name pattern of FILENAME* (located on the root directory) and copy on a directory on server-2. Later, I have to use this file for ETL loading... For this I tried using as below
/usr/bin/ftp... (8 Replies)
Discussion started by: dhruuv369
8 Replies
5. UNIX for Dummies Questions & Answers
I have 3 servers A, B, C and server B is having some files in /u01/soa/ directory, these files i want to copy to server C, and i want to run the script from server A.
Script(Server A) --> Files at Server B (Source server) --> Copy the files to Server C(Target Server).
We dont have RSA key... (4 Replies)
Discussion started by: kiran_j
4 Replies
LEARN ABOUT DEBIAN
xdevicebell
XDEVICEBELL(3) XDEVICEBELL(3)
NAME
XDeviceBell - ring a bell on a device supported through the input extension
SYNOPSIS
#include <X11/extensions/XInput.h>
Status XDeviceBell( Display *display,
XDevice *device,
XID feedbackclass,
XID feedbackid,
int percent);
display
Specifies the connection to the X server.
device
Specifies the device with which the bell is associated.
feedbackclass
Specifies the class of the feedback with which the bell
is associated.
feedbackid
Specifies the id of the feedback with which the bell is
associated.
percent
Specifies the volume in the range -100 to 100 at which
the bell should be rung.
DESCRIPTION
The XDeviceBell request causes the server to ring a bell on the
specified feedback of the specified device, if possible. The
specified volume is relative to the base volume for the bell.
If an invalid device is specified, a BadDevice error will be
returned. The feedbackclass and feedbackid parameters contain
values returned by an XGetFeedbackControl request and uniquely
identify the bell to ring. If a feedbackclass is specified that
does not support a bell, or if a nonexistent feedbackid is
specified, or a percent value is specified that is not in the
range -100 to 100, a BadValue error will be returned.
The volume at which the bell is rung when the percent argument
is nonnegative is: base - [(base * percent) / 100] + percent
The volume at which the bell rings when the percent argument is
negative is: base + [(base * percent) / 100]
To change the base volume of the bell, use
XChangeFeedbackControl.
XDeviceBell can generate a BadDevice or a BadValue error.
DIAGNOSTICS
BadDevice
An invalid device was specified. The specified device
does not exist, or has not been opened by this client
via XOpenInputDevice.
BadValue
An invalid feedbackclass, feedbackid, or percent value
was specified.
SEE ALSO
XChangeFeedbackControl(3), XBell(3)
05/15/2013 XDEVICEBELL(3)