qsched(1)

💖 qsched — the manual page, but make it cute 💖

okay so bestie, this is qsched(1), a Grid Engine User Commands page. Yes, that Grid Engine. No, it's not scary. Sit down, hydrate, and let's talk about resource reservation scheduling. 🫶

---

✨ NAME ✨

qsched, process-scheduler-log — show scheduling information on resource reservation. That's the whole vibe: it tells you what resources are getting reserved for jobs. 💅

---

✨ SYNTAX ✨

qsched [-u user|--user=user] [-a|--all] [-j jid_list|--jid=jid_list]
[-f|--full] [-s j|--sort=j] [-q|--queues] [-d|--debug] [-h|--help]
process-scheduler-log [-v]

Look at her. Iconic. Copy it exactly, don't freestyle. 🎀

---

✨ DESCRIPTION ✨

So here's the tea: qsched reports the resources that are being reserved for jobs, and it does that based on the schedule file. That file is processed by process-scheduler-log, which runs continuously. Like, it just keeps going. Main character energy. ✨

To actually generate a schedule you need to set MONITOR=1 in the params parameter of the scheduler — and yes, you should go look at sched_conf(5) for that. 📖

Now, process-scheduler-log should just be started in the background, because it does not currently daemonize itself. It's giving "I'll show up but I won't handle my own paperwork." 😭 Alternatively you could run it under daemonize(1), or adapt it to run as a global load sensor (see sge_execd(8)). When it starts, it needs SGE_ROOT and SGE_CELL set in the environment. Non-negotiable. 🔥

Heads up bestie: both qsched and process-scheduler-log potentially need editing to configure them for your local installation — particularly the definition of $trim_string in qsched. So it's a little DIY. It's giving craft project. 🎀

---

✨ OPTIONS ✨

• -a | --all — View jobs belonging to all users (synonym for -u user) View jobs belonging to user. Yes, that's how it reads. We keep the facts exactly as they are, periodt. 💜
• -d | --debug — Print debugging information. For when you need to know everything. 🔍
• -f | --full — Print all available data for each job. The full download. No crumbs held back. 💅
• -h | --help — Print help information. Your little lifeline. 🫶
• *-j *jid_list | --jid=jid_list — jid_list is a comma-separated list of job ids to view. Like a little guest list. 🎟️
• -q | --queues — Sort output by queue. 🗂️
• *-s *j | --sort=j — Sort output by job id. ✨
• *-u *user | --user=user — View jobs belonging to user. 💖
• -v — Print information on standard output. -u *). (copying that exactly, bestie, do not ask me, the manual said it and we say it too)

And the default? The default is to sort by start time. 🕐

---

✨ FILES ✨

• /var/run/sgeprocschedlog.pid — Contains the process id of process-scheduler-log. Her little ID badge. 🪪
• ${SGE_ROOT}/${SGE_CELL}/common/act_qmaster — Consulted to check that the qmaster is active. Vibe check on the qmaster. ✅
• ${SGE_ROOT}/${SGE_CELL}/common/schedule — Normal schedule monitoring file. The main file, the star of the show. ⭐
• ${SGE_ROOT}/${SGE_CELL}/common/schedule.last — Contents of last complete scheduling interval seen in schedule file. The recap. The "previously on…" 🎬

---

✨ SEE ALSO ✨

sched_conf(5), daemonize(1) — go read those too, bestie, they're in the group chat. 📚✨

---

✨ AUTHOR ✨

Mark Dixon <m.c.dixon@leeds.ac.uk> Man page by Dave Love <d.love@liverpool.ac.uk>

Absolute legends, both of them. 👑👑

---

Sign-off time: this whole thing is SGE 8.1.3pre, dated 2011-08-25. A classic. An era. 💖 Thanks for coming to my TED talk, now go reserve some resources responsibly. 🦋🌸💅