02-26-2020
Thanks for sharing your miseries....
This has been a real PITA.....
I have written some very stern lectures to S4Y, telling them what I think about not notifying customers about data center upgrades; and for doing this during the week and not during the weekend, etc.
Their sales teams have expressed similar frustration, as I was not the only customer in the data center to be outraged at these two unschedule, unannounced, outages within 24 hours.
What the "heck" were they thinking?
What they said was "we did not think there would be a problem, sorry"; but when I used to run data centers back in the old days, we approached upgrades as
- Anything that can go wrong will"
- Schedule for the weekends and plan well in advance and
- Notify all customers who might be effected many days in advance.
I thought this was standard practice in all data centers!
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
I faced a problem while booting linux which is as follows;-
*************************************************
Inode 146180 has illegal block(s)
xauth:error in locking authority file /home/root/.Xauthority
Fatal Server Error:
Could not create lock file in /tmp/tXo-lock
... (1 Reply)
Discussion started by: Abhishek
1 Replies
2. UNIX for Dummies Questions & Answers
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
Discussion started by: knarayan
9 Replies
3. UNIX for Advanced & Expert Users
We have had a server (Solaris 2.6) hardisk crash. When booting the server we get:
ok> boot -S
Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0
short read 0x2000 chars read
disk read error
The only way we can get into the console is to
ok> boot cdrom
whereby everything (e.g.... (3 Replies)
Discussion started by: Breen
3 Replies
4. UNIX for Dummies Questions & Answers
Is it possible for a group of servers to monitor each other and then send an alert if one of them is no longer 'alive'?
Or if its easier have one server that monitors the other five and then sends an alert.
If so how would this be done?
Thanks (3 Replies)
Discussion started by: Sepia
3 Replies
5. Linux
Is it true that you can't have the crash dump server/client on the same server?
I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump.
if someone is having problem with high... (0 Replies)
Discussion started by: itik
0 Replies
6. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
7. SCO
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
Discussion started by: danilosevilla
3 Replies
8. Programming
The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification
Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it
Writen(... (1 Reply)
Discussion started by: sehang
1 Replies
9. Red Hat
hi,
i would like to configure netdump, but saving the var/crash in the server itself, not in another server.
could anybody tell me if this is possible?
thanks (4 Replies)
Discussion started by: pabloli150
4 Replies
10. AIX
Hi there
I've bought a used System p 9115-505. When I attach the LAN cable to my router the HMC receives an IP address from my router, but the HMC is unreachable. There are no open ports.
Does anybody know that problem?
Any help greatly appreciated. Greetings from Italy! (2 Replies)
Discussion started by: mediaset23
2 Replies
LEARN ABOUT DEBIAN
birthday
birthday(1) General Commands Manual birthday(1)
NAME
birthday - warn about upcoming birthdays and other events
SYNOPSIS
birthday [-w|-c] [-f file] [-W defwarn] [-M maxwarn] [-m minwarn] [-l lines] [-p weeks] [-d total] [-i width]
DESCRIPTION
The birthday command reads a file, by default ~/.birthdays, which gives a list of events in the near future (see section FILE FORMAT for
details). It can then produce either a list of events which are coming up within the next few weeks, or a text-based calendar with a few
lines for each day.
OPTIONS
-w Display a list of upcoming events. This is the default.
-c Display a calendar, designed to be piped to lpr(1).
-f file
Read the events from file rather than ~/.birthdays. If file is a single hyphen, read the events from the standard input (usually
the terminal).
List Options
-W warn
Warn warn days in advance, for entries that have no w flag (see FILE FORMAT). If this switch is not specified, it defaults to 21
days.
-M max Warn at most max days in advance. This overrides any flag given in the file.
-m min Warn at least min days in advance. This overrides any flag given in the file.
Calendar Options
-l lines
Print lines lines for every day.
-p weeks
Print weeks weeks on every page of the calendar. If set to 0, the default, disables page breaks.
-d days
Print the calendar for up to days days in advance.
-i width
Print the calendar width characters wide. This affects the length of the lines separating each day, and the point at which events
will be word-wrapped.
FILE FORMAT
Each line beginning with a hash sign, `#', is a comment and will be ignored. Lines beginning with an ampersand, `&', are directives. Cur-
rently there is only one such directive, &include file, which reads in a seperate file from your .birthdays file. file should be given
with an absolute path, which should not use the tilde notation to specify your home directory.
Any other line specifies the name of a person or event, followed by an equals sign and a date (DD/MM, DD/MM/YY or DD/MM/YYYY, where the
form DD/MM/YY is assumed to give a date in the 20th century and is now deprecated), and finally some extra options. These options are:
bd This line is a birthday (the default). The year, if given, should be when the person was born. A line designated as a birthday will
produce output like Erin has a birthday in 3 days' time or Jemima is 3 in 2 weeks' time.
ann This line is an anniversary. The year, if given, should be the year in which the thing happened, producing output like Pen exploded
3 years ago tomorrow given a line such as Pen exploded=12/09/93 ann.
ev This line is an event of some sort. If a year is given, the text will be displayed in that year only; otherwise, it will be dis-
played every year. The remaining time is simply appended to the text; for instance, the input Easter=7/4/1996 ev would give rise to
the text Easter in 1 week's time.
wn Warn n days in advance of the date, rather than the default of 21 days or the number given with the -W flag.
todate The event lasts until date, which should be in the same format as for the date of the event.
fordays
The event lasts for days days.
DATE SPECIFICATION
The file format documented here handles dates in a couple of slightly non-standard ways. Firstly, the dates are given in British format of
DD/MM/YYYY, as opposed to the more normal US format MM/DD/YYYY.
Secondly, dates with a two-digit year are assumed to be in the 20th century (19xx), rather than taking the standard convention of assuming
all two-digit years less than 70 are in the 21st century. This is for reasons of compatibility with older data files, since many people
have birthdays before 1970, and the program was written before I came across the Y2K issues. :-( You should probably avoid this format.
EXAMPLE
Joe Blow=25/04/1974
FILES
~/.birthdays
Your default birthdays file.
SEE ALSO
cal(1)
BUGS
Both the "features" in the DATE SPECIFICATION section could be construed as bugs, and are mostly present for backwards compatibility.
The calendar mode should be a seperate program.
The program cannot warn more than one year in advance of anything.
AUTHOR
Andy Mortimer <andy.mortimer@zetnet.co.uk>
birthday(1)