Solaris

Hi All,


I am new to this forum and I am hoping someone will be able to help me


I have inherited a very old Solaris server that has a number of scripts around 500 in total.


I need to migrate the scripts to Linux but I would like to know which ones are currently being executed rather than migrating all 500 of them.


Is there a way in Solaris 5.9 to do this? I have googled and I believe there is a way in the later versions but not sure about this ancient version.


Any help would be greatly appreciated

It's always a good idea to search the forums before asking a question (which is also the forum rules).

See this prior thread and it should give you the clues you need:

last run time of any script

Hi Neo,


I read that post but I do not believe I can use accounting -see in the version of Solaris I have can I.


I tried the two ls commands but they don't give me what I need.


I need a list of all scripts executed on the Solaris box over the previous month or to turn something on that can monitor for the next month to see what is being run currently so I can work out what scripts to move to the Linux box.



Cheers

Sorry, I don't run Solaris 5.9 so I have no machine to help!

We do have the man pages available for 5.10 maybe you can find a reference there:

https://www.unix.com/man-page-sunos-repository.php

Thanks Neo,


I'll take a look and see if I can find anything


Cheers

If you look at this man page:

https://www.unix.com/man-page/sunos/1/ls/

You can see the ls option:

Code:

 -u	Uses time of last access instead of last modification for sorting (with the -t	option)  or  printing (with the -l option).

Seem like that kind of command, ls -u combined with find or a similar method will be helpful and meet your objective.

You're asking how to know which scripts run during the next month. So are users still using this system? If so, can't you ask them what commands they are running? If cron is automatically running stuff, why not pull up the crontabs and look at them?

Files are normally in:

Code:

/usr/spool/cron/crontabs

one file per username that has jobs scheduled. Although you shouldn't edit these files directly, they are perfectly readable with 'cat' for example.

Sorry if I'm on the wrong track here but I'm not clearly understanding your difficulty.

Please elaborate on the problem.