crontab+mplayer alarm clock Post: 302682227

Sponsored Content

Top Forums Shell Programming and Scripting crontab+mplayer alarm clock Post 302682227 by agama on Sunday 5th of August 2012 10:16:46 PM

08-05-2012

Registered User

Quote:

Originally Posted by hbar

@agama.

Putting a baclslash makes it work. Thanks. However, voume does not keep on increasing!

@Corona688

I'm using gnome desktop in ubuntu 12.04. I copied the structure from the internet and many places \dev\null is mentioned. Now, as I just said, it's working but volume is not increasing by 10% !

The way you have your command written, I wouldn't expect the volume to increase. The mixer command is invoked once, and if successful (&&) mplayer is invoked to play the mp3 looping through it 5 times.

If you want to bump the volume with each cycle through the file I would write a small script (alarm.bash or somesuch) and invoke that from cron. The script would look something like this:

Code:

#!/usr/bin/env bash
PLAYER=/usr/bin/mplayer
SONG=/home/hbar/Music/song.mp3

/usr/bin/amixer sset Master 35% >/dev/null 2>&1  # start with a default volume maybe??

for (( i = 0; i < 5; i++ ))
do
   /usr/bin/amixer sset Master 10%+ >/dev/null 2>&1
   $PLAYER -really-quiet -vo null $SONG >/dev/null 2>&1
done

In addition to Carona's suggestion, I'd toss in -really-quiet to cut the overhead of updates directed to /dev/null.

Last edited by agama; 08-05-2012 at 11:25 PM.. Reason: typo/added default volume setting

agama

View Public Profile for agama

Find all posts by agama

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

alarm

Hello I have a server HP ES40 with unix 5.1B, and if i open from Start-Programs-IN Tools-GUI/pfmalarm/Alarm-start monitoring , I receive this error message "IOR : STRING IS TOO LONG ! MAXIMUM SIZE = 1024" Anybody heard about this error? Thanks Alin

2. Shell Programming and Scripting

Scripting an alarm

Hi All, I am monitoring batch Processes running in UNIX environment. I use PuTTy to monitor the process running. I have to continuously monitor and look on the screen if some error has come or not. If an error comes FAILURE word is displayed instead of SUCCESS as shown below on the...

3. Shell Programming and Scripting

Alarm clock error while executing the script

I am executing perl script on Linux machine and the script is running for the last 5 hours and while running the script I had an error message in a single line Alarm Clock and the script got stopped. I havnt scheduled the script.I have executed the script manually. There is no syntax errors in...

LEARN ABOUT LINUX

alarm_handler

alarm_handler(3erl)					     Erlang Module Definition					       alarm_handler(3erl)

NAME

       alarm_handler - An Alarm Handling Process

DESCRIPTION

       The  alarm  handler  process is a gen_event event manager process which receives alarms in the system. This process is not intended to be a
       complete alarm handler. It defines a place to which alarms can be sent. One simple event handler is  installed  in  the	alarm  handler	at
       start-up, but users are encouraged to write and install their own handlers.

       The  simple  event  handler  sends all alarms as info reports to the error logger, and saves all of them in a list which can be passed to a
       user defined event handler, which may be installed at a later stage. The list can grow large if many alarms are generated. So it is a  good
       reason to install a better user defined handler.

       There  are functions to set and clear alarms. The format of alarms are defined by the user. For example, an event handler for SNMP could be
       defined, together with an alarm MIB.

       The alarm handler is part of the SASL application.

       When writing new event handlers for the alarm handler, the following events must be handled:

	 {set_alarm, {AlarmId, AlarmDescr}} :
	   This event is generated by alarm_handler:set_alarm({AlarmId, AlarmDecsr}) .

	 {clear_alarm, AlarmId} :
	   This event is generated by alarm_handler:clear_alarm(AlarmId) .

       The default simple handler is called alarm_handler and it may be  exchanged  by	calling  gen_event:swap_handler/3  as  gen_event:swap_han-
       dler(alarm_handler,  {alarm_handler,  swap},  {NewHandler,  Args})  .  NewHandler:init({Args, {alarm_handler, Alarms}}) is called. Refer to
       gen_event(3erl) for further details.

EXPORTS

       clear_alarm(AlarmId) -> void()

	      Types  AlarmId = term()

	      Clears all alarms with id AlarmId .

       get_alarms() -> [alarm()]

	      Returns a list of all active alarms. This function can only be used when the simple handler is installed.

       set_alarm(alarm())

	      Types  alarm() = {AlarmId, AlarmDescription}
		     AlarmId = term()
		     AlarmDescription = term()

	      Sets an alarm with id AlarmId . This id is used at a later stage when the alarm is cleared.

SEE ALSO

       error_logger(3erl), gen_event(3erl)

Ericsson AB							   sasl 2.1.9.3 					       alarm_handler(3erl)