Am 27.08.2013 um 09:39 schrieb Ng Shi Wei: > I dont get what you meant ? Can you explain it more details ? Which file i > should check whether mpiexec is included or not ?
`at` will send you an email with the stdout of the job by default. Hence the output of the `which` command should end up there. -- Reuti > Thank you in advance. > > Best Regards, > Shi Wei > > > From: re...@staff.uni-marburg.de > > Date: Tue, 27 Aug 2013 09:03:54 +0200 > > To: us...@open-mpi.org > > Subject: Re: [OMPI users] Unable to schedule an MPI tasks > > > > Am 27.08.2013 um 08:56 schrieb Ng Shi Wei: > > > > > Regarding the permission, I think I have the permission to run the at > > > command because I can use the at command to schedule other programs > > > except mpi program. > > > > Maybe the `mpiexec` isn't found and a submitted script could help: > > > > #!/bin/sh > > . ~/.profile > > which mpiexec # remove this line when it's working > > mpiexec ... > > > > (Replace ~/.profile with ~/.bash_profile or ~/.bash_login in case you use > > these. In case `mpiexec` is available even without these: is there > > something like /etc/profile which needs to be sourced?) > > > > -- Reuti > > > > > > > Is there any other scheduling command to schedule task? > > > > > > Thank you in advance. > > > > > > Best Regards, > > > Shi Wei > > > > > > --- Original Message --- > > > > > > From: "Ralph Castain" <r...@open-mpi.org> > > > Sent: 27 August 2013 11:33 > > > To: "Open MPI Users" <us...@open-mpi.org> > > > Subject: Re: [OMPI users] Unable to schedule an MPI tasks > > > > > > Perhaps I don't understand, but mpirun has no problem being executed > > > using the "at" command. Perhaps the problem is that you don't have > > > permission for "at"? Per the man page: > > > > > > The superuser may use these commands in any case. For other users, > > > permission to use at is determined by the files /etc/at.allow and > > > /etc/at.deny. > > > > > > If the file /etc/at.allow exists, only usernames mentioned in it are > > > allowed to use at. > > > > > > If /etc/at.allow does not exist, /etc/at.deny is checked, every username > > > not mentioned in it is then allowed to use at. > > > > > > If neither exists, only the superuser is allowed use of at. > > > > > > An empty /etc/at.deny means that every user is allowed use these > > > commands, this is the default configuration. > > > > > > You also might check to see what directory mpirun is executed from when > > > "at" actually runs, and that the path to both mpirun and your executable > > > are correct for that location. > > > > > > > > > On Aug 26, 2013, at 6:45 PM, Ng Shi Wei <nsw_1...@hotmail.com> wrote: > > > > > >> Hi all, > > >> > > >> Due to the time constraints, I would like to run the mpi program by > > >> scheduling the program to run on desired time using the "at" command. > > >> However, it seems that the mpirun doesn't execute the mpi program at the > > >> desired time using the "at" command. > > >> > > >> I would like to ask is there any other method to schedule a program to > > >> run ? > > >> For best, it can straight away starts the second mpi program once the > > >> previous program is finished. > > >> > > >> Hope to get some reply from you all. > > >> > > >> Thanks in advance. > > >> > > >> Best Regards, > > >> Shi Wei > > >> _______________________________________________ > > >> users mailing list > > >> us...@open-mpi.org > > >> http://www.open-mpi.org/mailman/listinfo.cgi/users > > > > > > _______________________________________________ > > > users mailing list > > > us...@open-mpi.org > > > http://www.open-mpi.org/mailman/listinfo.cgi/users > > > > _______________________________________________ > > users mailing list > > us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/users > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
