Sponsored Content
Top Forums UNIX for Advanced & Expert Users bigbrother monitoring:conn ssh on server clients goes purple green alternatively Post 302210221 by pankajd on Monday 30th of June 2008 10:54:14 AM
Old 06-30-2008
bigbrother monitoring:conn ssh on server clients goes purple green alternatively

i am using big brother 1.9i.some clients are shut down.but server and other clients are on and bb is running successfullly on all of them.But network tests like conn ssh,telnet etc are going purple for some time and become green for some time on all clients and server reports are not updating..i have bbdisplay and bbnet on same machine.BBOUT do not indicate any error.when rest of the clients are powed on,and monitored,then that problem do not arise.what can be the reason and solution.ping "-w3 -n -c1" is also tried ,it do not work ..can anybody please help me..
 

7 More Discussions You Might Find Interesting

1. Solaris

Solaris 8 server and Jumpstarting 2.6 clients

Ladies and Gentlemen: I have successfully configured a Solaris 8 server with Jumpstart! I can Jumpstart Solaris 8 client systems with no problem. My configuration is as follows: Jumpstart Server: Solaris 8 patched with Recommended Patches from June 05. I have installed Solaris 8 in... (4 Replies)
Discussion started by: rambo15
4 Replies

2. Cybersecurity

List of HTTP/FTP-clients on a server

The other day, a friend of mine had his Linux webserver compromised because he was running a vulnerable PHP-script. The "hacker" had used a malformed URL to include a wget-command to fetch some stuff off the net and install it in /dev/shm where it ran undetected. Fortunately, the webserver ran as a... (2 Replies)
Discussion started by: indo1144
2 Replies

3. Shell Programming and Scripting

echo to connected ssh clients

Hello, i have a network device that users connect to using ssh. I have a script that connects to the device and has to echo something to other connected people. How can this be established? ssh user@device 'echo Hello > /dev/console' doesn't seem to do the trick. (2 Replies)
Discussion started by: trafo23
2 Replies

4. UNIX for Advanced & Expert Users

Quest on NFS with 1 Server & 2 Clients

Hello; I work now with a team which has based her "applications" on the following schema: 1 NFS client C1 (linux redhat 5) writes a file fic.dat on a NFS SERVER S (RH 5) Another NFS client C2 is waiting for the same file fic.dat (on NFS server S1), and, when "fic.dat" appears, then makes... (8 Replies)
Discussion started by: SolarMax
8 Replies

5. IP Networking

Some clients cannot ping UNIX server

All of sudden in this morning, some computers could not connect to our UNIX server while other still could. Some computers could ping the server while some could not. Same on the server side. It could ping some clients but not some. All Windows clients could ping each other. And more, the... (1 Reply)
Discussion started by: jonapa
1 Replies

6. Programming

Clients - Server ( UDP )

Hello, I have a question: I want to create a n client to one server connection. This is the client-server algorithm. Enybody help to make the changes? (0 Replies)
Discussion started by: MaHmur
0 Replies

7. Shell Programming and Scripting

Opening different UNIX ssh clients simentously

Hi Team , Please advise is thee any ssh terminal open source software by which I can watch all the 4 unix boxes at same time and whatever i will type will get printed on all the 4 different unix boxes at the same time for example one i know is Moba Xterm ssh client software I have share the url... (1 Reply)
Discussion started by: tuntun06060606
1 Replies
HYLAFAX-SHUTDOWN(5)						File Formats Manual					       HYLAFAX-SHUTDOWN(5)

NAME
etc/shutdown - server shutdown control file DESCRIPTION
If the file etc/shutdown is present it describes when a HylaFAX server is to be shutdown and may contain a descriptive message to return to clients explaining the reason for the shutdown. This file is used by the hfaxd(8) program. The file has the following format: <year> <month> <day> <hour> <minute> <deny> <disconnect> <shutdown message text> The first line defines the date and time the server should be shutdown and the time preceding at which unprivileged clients should be denied service or disconnected; these fields are described in more detail below. Any lines that follow the first are taken as the text of a message to return to clients when notifying them of a scheduled shutdown or when denying them service. <year> The decimal year; e.g. 1996. <month> The decimal month; e.g. 10 for October. <day> The decimal day of the month in the range [1..31]. <hour> The decimal hour since midnight; in the range [0..23]. <minute> The decimal minute after the hour; in the range [0..59]. <deny> The time prior to the shutdown time at which to deny service to unprivileged clients. This value is specified as decimal number in the form HHMM; e.g. 130 for 1 hour and 30 minutes. <disconnect> Time time prior to the shutdown time at which to disconnect unprivileged clients that are logged in to the server. This value is specified as a decimal number in the form HHMM. NOTES
This file is typically created using the ``SHUT'' command supported by hfaxd(8). SEE ALSO
hfaxd(8), hylafax-server(5) January 18, 1996 HYLAFAX-SHUTDOWN(5)
All times are GMT -4. The time now is 07:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy